3 ms·
Reproducibility with a well-written Docker image is well worth it over "cp-ing config files" shiver. Docker isn't Kubernetes -- it's not that complicated.
by boardwaalk 6y ago
Reproducibility with a well-written Docker image is well worth it over "cp-ing config files" shiver.
Docker isn't Kubernetes -- it's not that complicated.
- u801e 6y agocp-ing config files is typically done by using config management like puppet, chef, ansible, or saltstack via templating based on server type, location, etc.
- Seirdy 6y agoWhat's so risky about cp-ing config files as opposed to typing "COPY" or mounting a volume in a Dockerfile? If you use a distro like Debian you shouldn't be worried about breaking changes, especially if you're subscribed to updates/relnotes for the critical parts of your stack (e.g., an announcements mailing list). Those are good practices to have regardless of your platform.
- kvz 6y agoDocker images aren’t built in a reproducible way unless you use something like Nix to create them