Replies: 1 comment 1 reply
-
|
you can use custom networks the subnet for container is whatever you want and then you just need to set a custom route to your local subnet using the container subnet gateway keep in mind routes are set in the container namespace, any container that you give CAP_NET_ADMIN could add a default route themselves (i.e. only safe when not using --privileged or --cap-add CAP_NET_ADMIN) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello.
There is a rootless podman container.
The task is to make sure that there is no default route inside the container, but there is a network and access to the Internet.
Internet access means access to the router subnet: 192.168.1.0/24.
The following options do not help:
the network is created and the default route is copied from the host.
It turns out to be done like this:
But this must be done every time, which is not a convenient or smart solution.
Please tell me, is there any solution so that there is no default route?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions