[asabil]

It's quite unfortunate that this article mixes up what's necessary for podman quadlets with coreOS concepts.

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`. And this of course also supports per-user rootless containers as described in [1].

[1]: https://www.redhat.com/sysadmin/quadlet-podman

[pcthrowaway]

I agree, and I think the author was unfortunately using coreOS because it's uncommon for cloud providers to have coreOS images nowadays, and therefore a good opportunity for him to slip in a referral code for VULTR.

Is coreOS even maintained any more? I wouldn't expect it to be very secure if the most recent VM images were built in ~2020.

Would love another writeup just using Ubuntu or some other bog-standard Linux distro.

[nine_k]

CoreOS was acquired by Red Hat, and now "Fedora CoreOS".offers similar concepts.

Conveniently, RH also invented both Podman and systemd.

[yencabulator]

Note: similar, but definitely not the same. The real continuation of CoreOS was Flatcar Linux (https://www.flatcar.org/), but then the company behind that was bought by Microsoft (https://kinvolk.io/blog/2021/04/microsoft-acquires-kinvolk/) and I really don't expect much of them anymore...

[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.

[snapplebobapple]

Is there an alpineos equivalent with systemd? I have grown to adore that os for virtual machines running docker with compose.