You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(ci): add docker-proxy binary and use dedicated DinD socket
The first canary run revealed two issues:
1. dockerd failed to start because docker-proxy was not extracted from
the Docker static binary tarball. Add it to the extraction list.
2. The GitHub Actions runner injects its own Docker socket into job
containers. Without an explicit DOCKER_HOST, the openshell CLI
connected to the runner's host Docker daemon instead of our DinD
daemon. Start dockerd on a dedicated socket (/var/run/dind.sock)
and export DOCKER_HOST so all subsequent steps use it.
0 commit comments