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

Note Detail

Reply to @bajax@baj.ax
shibao@shibao@shitposter.world (2026-10-25 10:40:16)
@bajax @phnt then don't, just treat the `Dockerfile` as an instruction list with no bullshit, just commands. i prefer that over super long winded installation scripts that need to explain all the steps instead of just giving me commands to run
---Reply---
[msg] Bajax@bajax@baj.ax (2026-10-25 10:57:25)
@shibao @phnt I'm not gonna be able to explain to you why that's unacceptable lol.  it amounts to "hassle" but I suspect you're gonna have what amounts to a moral objection to that so I'll just leave it there.  (is there a way to have a patch you can set on dockerfiles so you can use automatic updates and automatically apply your changes?  then you only have to get into it if you touched something that changed)

I've started using ansible to set up shit, maybe I can have an LLM routine that converts dockerfiles into roles or something.

---Replies---

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