News for hackers. Stuff that matters.

A comment on File Permissions: A painful side of Docker (2019). Parent comment

Re:File Permissions: A painful side of Docker (2019) by q3k on Monday May 31, 2021 @11:25AM (#27344967)
> You can go the extra mile and turn the UID:GID into build args like the original parent and you're good to go.

That doesn't help you if you're attempting to use pre-built/existing Docker images that are not built internally and make the assumption that “1000:1000 is good enough”. You then not only have to hack around Docker limitations, but also around someone else's broken assumption.

[ Parent | on HN ]
Re:File Permissions: A painful side of Docker (2019) by nickjj on Monday May 31, 2021 @01:26PM (#27346312)
> That doesn't help you if you're attempting to use pre-built/existing Docker images that are not built internally

Most pre-built images that I've come across don't require bind mounts to function.

Images like PostgreSQL aren't affected by this because you can use a named volume, and most pre-built applications that are shipped as images tend to store their state in a database and don't require bind mounts to function.

[ Parent | on HN ]