[nisa]

> With quadlets, the only thing required is to drop a `.container` file in the right place and you end up with a container properly supervised by `systemd`.

Is it? He defines a .network file in that butane config without it won't work. Not really obvious. I'm sure this has a use-case and it's nice to have but personally I'm not convinced. You can switch on user-namespaces in docker-daemon or even run docker itself rootless - I guess if you are in Redhat land and use podman anyway it's an alternative but for instance where is this thing logging into? journalctl --user? Can I use a logshipper like loki with this? Is there something like docker compose config that shows the fully rendered configuration? I personally don't see the point and it feels like overly complicated.

[twic]

It will log to wherever you configure. By default, the journal. And [0]:

> Currently, Promtail can tail logs from two sources: local log files and the systemd journal (on AMD64 machines only).

Whether it supports user services, I don't know.

[0] https://grafana.com/docs/loki/latest/send-data/promtail/

[hobo_mark]

butwhat?

> Butane (formerly the Fedora CoreOS Config Transpiler, FCCT) translates human readable Butane Configs into machine readable Ignition Configs.

igwhat? Why, WHY?!

[9dev]

Right?? They wrung everything possible out of that metaphor, and then some more, and then another bit more.

[INTPenis]

.network is only required if you need a network, just like you define networks in docker compose for some containers to have one shared private network.

[nisa]

yeah spend some time on the docs for this and it's pretty straight forward - the article and the repo kind of omits this but it's also for a different usecase. Was just irritated when I wrote that comment. It's really some oci container to systemd shim system that uses podman.