[flagged]
Quadlets might make me finally stop using docker-compose
21–30 of 212 posts
Re: Quadlets might make me finally stop using docker-compose
#22Say what you want about docker compose, but when I see the amount of scaffolding necessary for this, with so many catch words like butane or ignition, I’m happy with my good ol’ docker composé file where everything is neatly organized. In one glance I can see what is deployed, depends on what and what net / volume is used. For simple projects, it’s hard to beat
Yes! Can we talk about projects consistently deciding to invent new nomenclature for their entities or products. Is it an effort to lock you in to their system?
Just call things what they are.
Re: Quadlets might make me finally stop using docker-compose
#23Overall this looks really good but it also obfuscates whether how & where this really integrates with systemd. Maybe everything is this easy & good. Maybe this is an /etc/systems/system/WordPress.quadlet file, part & parcel to everything else in the systemd-verse. But it doesn't say clearly whether it is or isn't. It's an acontextual example. I think it's powerful tech either way, but so much of the explanation is mi…
Quadlet uses SystemD Generators [1] feature. Generators are a way to convert non-systemd-native configuration extensions (like containers, volumes and networks in case of quadlets) into regular systemd-native configuration like service unit-files. The quadlet generator converts the podman extension for systemd into regular service file that you can examine yourself. Non-root podman container services are in /run/user//systemd/generator. Here is a blog post that describes the design in detail (slightly dated): [2]
[1] https://www.freedesktop.org/software/systemd/man/systemd.gen...
[2] https://blogs.gnome.org/alexl/2021/10/12/quadlet-an-easier-w...
Re: Quadlets might make me finally stop using docker-compose
#24[flagged]
What? If you use containers this simplifies the stack rather than complicating it. Instead of kubernetes and other popular tools it's just rootless podman and systemd which is already there.
I'm using a similar setup and this excites me. It's too new to be in my repository but as soon as I get an extra hour I'll compile it and take it for a spin.
Re: Quadlets might make me finally stop using docker-compose
#25Say what you want about docker compose, but when I see the amount of scaffolding necessary for this, with so many catch words like butane or ignition, I’m happy with my good ol’ docker composé file where everything is neatly organized. In one glance I can see what is deployed, depends on what and what net / volume is used. For simple projects, it’s hard to beat
I was confused by this article in the beginning, it does a pretty bad job at drawing a distinction between the pure quadlet example at the start and the example of using CoreOS to build and launch a VM that starts containers. The basic usage of podman quadlets is putting an `app.container` in `/etc/containers/systemd/` containing something like the first snippet and then starting the unit. For someone familiar with s…
I'm still not clear whether quadlets are a feature of Podman or systemd...
The reliance on systemd is an issue on its own. Much has been said about its intrusion in all aspects of Linux, and I still prefer using distros without it. How can I use this on, say, Void Linux? Standalone Podman does work there, but I'm not familiar if there were some hacks needed to make it work with runit, and if more would be needed for this quadlet feature.
Re: Quadlets might make me finally stop using docker-compose
#26Why the name quadlets? Classical definition: > A word consisting of four bytes Quad implies 4 something or rather. What does it refer to here? 4 sections of configuration?
Maybe they mean Quadrant.
Re: Quadlets might make me finally stop using docker-compose
#27[flagged]
[deleted]
Re: Quadlets might make me finally stop using docker-compose
#28It'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].
Re: Quadlets might make me finally stop using docker-compose
#29To me, this big problem with Docker is that it does a ton of changes to my system, even when I don't use it.
It runs a daemon, it uses a bunch of IPs, it mounts a ton of stuff ...
Is there a reason for all that noise and complexity?
There can't be a reason until I run a container, right? And even then, it seems way too much.
Is it different when using Quadlets?
Re: Quadlets might make me finally stop using docker-compose
#30[flagged]
What? If you use containers this simplifies the stack rather than complicating it. Instead of kubernetes and other popular tools it's just rootless podman and systemd which is already there. I'm using a similar setup and this excites me. It's too new to be in my repository but as soon as I get an extra hour I'll compile it and take it for a spin.
If you want to really simplify using containers, you could just use systemd-nspawn.