Skip to content

network: use rootless user check for config paths#2547

Closed
vfreex wants to merge 1 commit into
containers:mainfrom
vfreex:network-rootless-user-paths
Closed

network: use rootless user check for config paths#2547
vfreex wants to merge 1 commit into
containers:mainfrom
vfreex:network-rootless-user-paths

Conversation

@vfreex

@vfreex vfreex commented Jun 20, 2026

Copy link
Copy Markdown

Dependency support for the main Podman fix: podman-container-tools/podman#28995

Bug report: podman-container-tools/podman#18783

Network config/runtime path selection should distinguish a real rootless user from UID 0 running inside a nested user namespace.

This changes netavark and CNI config path selection to use rootless-user semantics, matching Podman's behavior for nested root: unshare.IsRootless() is only treated as rootless networking when the originating rootless UID is non-zero. UID 0 in a delegated container environment should continue to use rootful network paths.

Tests

  • GOOS=linux go test -c -o /private/tmp/common-network.test ./libnetwork/network
  • GOOS=linux go test -tags cni -c -o /private/tmp/common-network-cni.test ./libnetwork/network

Signed-off-by: Yuxiang Zhu <vfreex@gmail.com>
@github-actions

Copy link
Copy Markdown

This repository has been migrated to https://github.com/containers/container-libs. Please open your PR there.

@vfreex

vfreex commented Jun 20, 2026

Copy link
Copy Markdown
Author

Replacement PR in the migrated repository: podman-container-tools/container-libs#932

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant