Fix runtime iptables selection for non-root Docker-in-Docker entrypoints - #1747
Open
Kaniska (v-Kaniska244) wants to merge 2 commits into
Open
Kaniska (v-Kaniska244) wants to merge 2 commits into
Kaniska (v-Kaniska244) wants to merge 2 commits into
Conversation
Kaniska (v-Kaniska244)
marked this pull request as ready for review
October 6, 2026 06:33
This branch has not been deployed
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
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.
What does this PR do?
Fixes Docker-in-Docker runtime iptables selection when the feature entrypoint runs as a non-root user reported in an issue devcontainers/images#2033 in images repository for universal image.
Observed the below failures in the Codespaces creation log with universal image:
Docker-in-Docker v4 selects the iptables backend at container startup. Images such as Universal configure
codespaceas thecontainerUser, causingupdate-alternativesto fail with permission errors underalternatives.This change:
sudo_ifbefore runtime iptables selection.update-alternativesmutations throughsudo_if.4.1.2to4.1.3.Testing
Added an isolated Ubuntu Noble test that:
ubuntuuser.codespaceuser throughcommon-utils.containerUserandremoteUserascodespace.common-utils.codespace.The scenario is excluded from shared test jobs and runs through the dedicated
iptables-isolationworkflow matrix, consistent with the existing Ubuntu iptables tests.Validated with:
The test passes without
update-alternativespermission errors.