Open icsy7867 opened 10 months ago
You need privileges to do that and Enroot by design doesn't grant you more privileges that you have. There's no network namespace by default either for the same reason.
You can run the container as root (superuser) if your enroot config allows it. Alternatively you can unshare a network namespace inside the container, but you would have to wire it to your host network somehow (slirp, veth, etc)
Hello! I have a rather strange implementation. I am trying to connect the jail to another host via a wireguard tunnel. If using docker, it works fine. However enroot does not seem to allow the creation of network interfaces.
I was curious if anyone knew of a setting or a way to make something like this work. Thanks!