Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @bajax@baj.ax
shibao@shibao@shitposter.world (2026-10-25 11:01:54)
@bajax @phnt the whole point of docker is that it create a repeatable setup in an environment like an ansible playbook, except every time the docker image is built you're actually executing the ansible playbook and you're guaranteed to get the same thing because you're starting from a fresh instance of ubuntu or alpine or whatever the base image is from the beginning. the "hassle" is the load on maintainers that people who can't linux and expect the maintainers to do their weird custom linux admin for them

>suspect you're gonna have what amounts to a moral objection
what? this is all practical, not moral. you're the one moralizing about how a repeatable setup is bad and you won't explain why to me because you view it as "bloat" or something and want the maintainers to handhold you on making guides so that you can use your weird custom linux setup rather than using what the maintainer has decided to support for their software
---Reply---
shibao@shibao@shitposter.world (2026-10-25 11:05:36)
@bajax @phnt i don't get why you're shitting on this thing that you don't understand fully

>is there a way to have a patch you can set on dockerfiles so you can use automatic updates and automatically apply your changes?
yes you create a custom dockerfile that just like how the normal dockerfile starts from the ubuntu image and adds commands and whatnot for it, you just have a custom dockerfile that starts with whatever software's dockerfile you're using and then add commands on top of it, which basically amounts to you following a software's installation guide and then deciding to do more commands after you're done with it. but with docker, it's repeatable and idempotent (or supposed to be in theory at least)

---Replies---

shibao@shibao@shitposter.world (2026-10-25 11:07:15)
@bajax @phnt if you want to change something in the original dockerfile, just copy and paste it and then make your modifications and then ideally merge it back into the main repo or push it up on your own repo, this is the equivalent of making your own guide, but you can keep running it, when you do docker build it's the equivalent of spinning up a new VPS and doing the installation instructions from scratch automatically, and then you can run tests against it to check if it works. but then you don't have to spin up a second device with a second kernel with docker. that's it, that's all the "bloat" that everyone is complaining about