File Permissions: A painful side of Docker (2019)

Re:File Permissions: A painful side of Docker (2019) by oauea on Monday May 31, 2021 @12:42PM (#27345881)

Sure, great, let me just rebuild all my docker images on every single machine they run on thereby completely defeating the point of having images in the first place.

[ Parent | on HN ]

Re:File Permissions: A painful side of Docker (2019) by dandarie on Monday May 31, 2021 @02:00PM (#27346646)

You start from a base image of your choice. You only build the user replacement part.

You run docker-compose build ONCE and you're set. On my machine, it takes five seconds.

Heck, you can even run docker-compose build everytime you start the application, it will use the cached build and take less than one second.

---

Correction: the docker-compose up -d takes care of the build process the first time it runs.

Literally, it takes more to complain about the issue than build the image ONCE.

[ Parent | on HN ]

Re:File Permissions: A painful side of Docker (2019) by oauea on Tuesday June 01, 2021 @12:03AM (#27350629)

And reproducibility goes straight out the window. And how do you even interop this with kubernetes?

[ Parent | on HN ]

Re:File Permissions: A painful side of Docker (2019) by dandarie on Tuesday June 01, 2021 @05:57AM (#27352379)

The solution is for docker-compose (or plain docker).

I don't think the reproducibility is out. It's the same app, the same image, the same intended user, you just inject, once, the local user and group ids.

[ Parent | on HN ]