Skip to content
Discussion options

You must be logged in to vote

I don't think this is possible in the host network namespace, while you can add capabilities inside the container the kernel knows that you (a user) is not allowed to modify the host network namespace.

Rootless podman cannot gain more privileges that your user already has so it is impossible to modify the host network namespace or open a raw socket in it. If it were this would be a huge security problem.
The sysctl allows you only to bind low ports, e.g. udp or tcp but I think dhcp requires a raw socket so it shouldn't matter in this case.

I think the only way to make it work is to run podman as root.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@Rabbit234
Comment options

@rhatdan
Comment options

Answer selected by Rabbit234
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants