Half the problem comes from an arbitrary restriction I put on myself. I wanted this to work from a completely unprivileged Docker container. Normally Docker doesn't give guest containers things like CAP_NET_ADMIN, which is needed to do things with TUN/TAP devices. I wanted to make the container image so that all you needed to do was:
docker run --rm -it xena/docker-uml
and then you'd suddenly have an entirely working user mode linux system right there. I mainly want to see how far the rabbit hole goes from a completely user level. TUN/TAP devices require CAP_NET_ADMIN, so they are not allowed in this case. Thus I chose Slirp.
Hi, author of the post here. Sorry I'm not the best with Russian, so I'll be using Google Translate to understand comments here and I'll answer questions in English.
I wasn't aware of that, thanks!
I'd absolutely love if that was the case. It's a shame that we live in a world where we can't do that.
Half the problem comes from an arbitrary restriction I put on myself. I wanted this to work from a completely unprivileged Docker container. Normally Docker doesn't give guest containers things like
CAP_NET_ADMIN, which is needed to do things with TUN/TAP devices. I wanted to make the container image so that all you needed to do was:and then you'd suddenly have an entirely working user mode linux system right there. I mainly want to see how far the rabbit hole goes from a completely user level. TUN/TAP devices require
CAP_NET_ADMIN, so they are not allowed in this case. Thus I chose Slirp.