Container/host uid contamination

[lgrosz]

crops/poky-container has a couple scripts, see poky-entry.py, which avoid contaminating the build volume with container uids.

This seems like a standard problem in the docker world, so see if there's some standard way of solving it. Requirements would be...

• Image should not have to be rebuilt per user
• The image should not have to use the sudo package
• bitbake must be ran as non-root

[lgrosz]

This post details two solutions...

• Using build arguments to change the added users uid and gid at build-time

This options makes pushing images to registries kind of pointless, and would be more of a hassle for the user, especially if the build has a bunch of build arguments like TARGET_PLATFORM later-on.

• Using a script which looks at an attached volumes and modifies the user accordingly.

This is what crops/poky-container does. It may require sudo, maybe not depending on how the dockerfile is setup.

[lgrosz]

fixuid is an application which can do this fixing without it being a homebrewed script.