fix: mount Docker socket in devcontainer to fix bazel run (#248)#258
Merged
Conversation
Fixes #248 When running inside the devcontainer, the generated run_docker.sh script calls and . These fail because the host Docker socket (/var/run/docker.sock) was not mounted into the container, resulting in: failed to connect to the docker API at unix:///var/run/docker.sock; dial unix /var/run/docker.sock: connect: no such file or directory Add a bind mount for the Docker socket in .devcontainer/devcontainer.json so that Docker commands inside the devcontainer communicate with the host Docker daemon.
akshaylg0314
requested review from
AlexanderLanin,
FScholPer,
MaximilianSoerenPollak,
PiotrKorkus,
antonkri,
dcalavrezo-qorix,
lurtz,
nradakovic,
opajonk and
pawelrutkaq
as code owners
|
The created documentation from the pull request is available at: docu-html |
PiotrKorkus
reviewed
Jun 9, 2026
PiotrKorkus
approved these changes
Jun 9, 2026
Contributor
|
QNX download fail is unrelated to the change |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Running bazel run //images/linux_x86_64:run inside the devcontainer fails after a successful build with:
failed to connect to the docker API at unix:///var/run/docker.sock; dial unix /var/run/docker.sock: connect: no such file or directoryRoot Cause
The runners/docker_x86_64/scripts/run_docker.sh script (invoked by the :run target) calls docker load and docker run to load and start the OCI image. The devcontainer was running without access to the host Docker daemon because .devcontainer/devcontainer.json did not mount the Docker socket.
Fix
Added a mounts entry in .devcontainer/devcontainer.json to bind-mount the host socket at /var/run/docker.sock into the container. This allows Docker CLI commands inside the devcontainer to communicate with the host Docker daemon (Docker-outside-of-Docker pattern).
Testing
Fixes #248> failed to connect to the docker API at unix:///var/run/docker.sock;
dial unix /var/run/docker.sock: connect: no such file or directory