Hi,
This question got a bit overlooked, so I’m asking it here in its own thread.
According to the official documentation, I’m supposed to create a series of directories with root:root
permissions like this:
$ sudo mkdir -p \
/srv/e/src \
/srv/e/zips \
/srv/e/logs \
/srv/e/ccache
And then I launch the build using sudo docker run
:
$ sudo docker run \
-v "/srv/e/src:/srv/src" ...
I have doubts as to the permissions of this operation. Normally when you build stuff (distribution packages, kernel, whatever) it’s just wrong to launch your build as root
. Under Unix/Linux you build things as a mere mortal user and then just use superuser permissions to install the stuff.
Another detail that made me cringe a bit was the sudo docker run
instruction in the documentation. In a sane setup, your mortal user is already a member of the docker
system group, and it’s just wrong to launch docker
using sudo
.
Is that just a case of permission sloppiness from the developers ? Or do I really really need full root
permissions just to build /e/OS from source using Docker ?
Any suggestions ?