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
LGTM, no running errors, I can read/write in the bind mounted data folder.
Adding netns support to this container
Host side
Create a simple network namespace using ip : ip netns add userns. This command spwan a network namespace handler in /var/run/netns/userns (#37 for netns information)
The network namespace you created belongs to the host user namespace,
so your unprivileged user can't join it. What you want to do is have
the unprivileged user create both the user namespace and the network
namespace (either in the same clone(2) call, or from within the user
namespace). For a not-quite-OCI example of unprivileged network
namespaces, see 1. And for one way to connect that to the host
network namespace using a privileged host user, see 2.
Adding netns support to containers fails due to userns.
Basic userns container
Host side
Using a userns user
According to this issue #252, all files listed bellow are owned by userns:userns
Config file
Container side
LGTM, no running errors, I can read/write in the bind mounted data folder.
Adding netns support to this container
Host side
Create a simple network namespace using ip :
ip netns add userns
. This command spwan a network namespace handler in /var/run/netns/userns (#37 for netns information)Tell runc to use this handler
runc start command now fails with this error
The text was updated successfully, but these errors were encountered: