Removes the logic about users and permissions for docker introduced in #495.
Instead, introduces a docker.run_as option which can run the docker container as a specific user (root, current unix user, or a specific other user).
The problem with the previous implementation was that it did not work if the docker images were meant to be shared, as the creators uid/gid were embedded in it. I tried to look for a general solution that would work in both cases, but in doing so I found that docker is inconsistent. I had two users, both on ubuntu 22.04.02 and docker cb74dfc, run:
One had the root file listed under her own name on the host machine while the second command gave a permission error.
The other had the root file listed under root on the host machine while the second command created it under his name.
Help is welcome, but until then we'll leave it configurable.
Additionally:
shrink the docker images by leaving out some additional directories.
no longer force docker run as root in aws explicitly, but use the 'default'.
Removes the logic about users and permissions for docker introduced in #495. Instead, introduces a
docker.run_asoption which can run the docker container as a specific user (root, current unix user, or a specific other user).The problem with the previous implementation was that it did not work if the docker images were meant to be shared, as the creators uid/gid were embedded in it. I tried to look for a general solution that would work in both cases, but in doing so I found that docker is inconsistent. I had two users, both on
ubuntu 22.04.02anddocker cb74dfc, run:One had the
rootfile listed under her own name on the host machine while the second command gave a permission error. The other had therootfile listed underrooton the host machine while the second command created it under his name. Help is welcome, but until then we'll leave it configurable.Additionally: