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
All rules_docker rules that communicate with the Docker daemon, at least:
container_image
container_pull
container_run_and_commit
container_flatten
container_layer
install_pkgs
add_apt_key
Is this a regression?
I'm not aware of prior versions where this worked correctly.
Description
When --sandbox_default_allow_network=false and running in --spawn_strategy=linux-sandbox, the rules_docker rules cannot communicate with the Docker daemon because the rules do not declare requires-network in their execution_requirements.
🔬 Minimal Reproduction
tbd
🔥 Exception or Error
ERROR: /runner/_work/.../BUILD:13:14: Action path/to/target.tar failed: (Exit 1): target.sh failed: error executing command bazel-out/k8-fastbuild-ST-fff/bin/path/to/target.sh
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
Cannot connect to the Docker daemon at tcp://localhost:2376. Is the docker daemon running?
Some of the rules_docker rules do not provide a meaningful mnemonic -- the rule that generates .tar and add_apt_key, which makes a workaround difficult. At least for my repo, a sufficient workaround is to spec a number of strategy_regexp values and drop back to processwrapper-sandbox, which cannot enforce the network restrictions:
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_docker!
🐞 bug report
Affected Rule
All rules_docker rules that communicate with the Docker daemon, at least:
Is this a regression?
I'm not aware of prior versions where this worked correctly.
Description
When
--sandbox_default_allow_network=false
and running in--spawn_strategy=linux-sandbox
, the rules_docker rules cannot communicate with the Docker daemon because the rules do not declarerequires-network
in theirexecution_requirements
.🔬 Minimal Reproduction
tbd
🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules_docker version:
Anything else relevant?
Some of the rules_docker rules do not provide a meaningful mnemonic -- the rule that generates
.tar
and add_apt_key, which makes a workaround difficult. At least for my repo, a sufficient workaround is to spec a number of strategy_regexp values and drop back to processwrapper-sandbox, which cannot enforce the network restrictions:The text was updated successfully, but these errors were encountered: