7 ms·
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
by dandarie 5y ago
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.
- oauea 5y agoAnd reproducibility goes straight out the window. And how do you even interop this with kubernetes?
- dandarie 5y agoThe 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.