Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Quadlets might make me finally stop using docker-compose

major.io

Post reply on HN
Print view View original

51–60 of 212 posts

Re: Quadlets might make me finally stop using docker-compose

#51

Post by jve »

v3ss0n wrote: post #46
TekMol wrote: post #29

To 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?

What worse is , it screws up the firewall rules. Podman avoid that so , quadlets should be fine? Podman supposed to be drop-in replacement for docker but - last try (4 months ago) of podman to run our development docker containers fails to build so i think Podman is still far away from docker replacement.

Yeah, I also tried ~months ago. To be fair, I'v only tested out dev containers with docker, so I'm too weak to debug things what went wrong.

Any article out there on how to have windows + wsl2 + podman + vscode devcontainers working?

Re: Quadlets might make me finally stop using docker-compose

#52

Post by INTPenis »

nisa wrote: post #34
asabil wrote: post #28

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

> 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 ro…

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

Re: Quadlets might make me finally stop using docker-compose

#53

Post by hexo »

gigatexal wrote: post #35
imiric wrote: post #25

Earlier quoted context omitted.

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…

I mean the best part about open source and Linux is that you have choice. Do you want to run an OS devoid of SystemD? Fine. Will you be going against the tide and leaving a large part of the ecosystem behind? Yup. I’ve chosen to embrace systemd and learn it as it is the defacto standard it seems rather than fight what I think is a futile war against it. That being said. I won’t force you to use it if you don’t. But I…

systemd is extremely intrusive. anything dependent on it is a failure.

Re: Quadlets might make me finally stop using docker-compose

#54

Post by INTPenis »

I started using quadlets for new system designs a month ago and I feel like I'm neck deep in it now.

My conclusion is that there is absolutely no reason to stop using docker-compose if your developers are comfortable running one command, on one file, in one git root.

Quadlets are basically docker compose, in systemd. They've finally done it, systemd has it all and now it even has docker compose. ;)

That's really all it is in practice. I'm going to continue using it because I'm a RHEL kinda guy, but don't make it up to be magic.

Re: Quadlets might make me finally stop using docker-compose

#55

Post by Grimburger »

v3ss0n wrote: post #46
TekMol wrote: post #29

To 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?

What worse is , it screws up the firewall rules. Podman avoid that so , quadlets should be fine? Podman supposed to be drop-in replacement for docker but - last try (4 months ago) of podman to run our development docker containers fails to build so i think Podman is still far away from docker replacement.

Docker's firewall modifications are incredibly obnoxious and at the top of the list of gripes for me.

Re: Quadlets might make me finally stop using docker-compose

#56

Post by sofixa »

TekMol wrote: post #29

To 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?

> Is there a reason for all that noise and complexity?

To make it simple at the point of use. If developers had to configure firewalls and bind mounts for Docker to work, it never would have taken off as much as it did.

Re: Quadlets might make me finally stop using docker-compose

#57

Post by sofixa »

rewmie wrote: post #16
frej wrote: post #9

Nitpick you wonder why yaml is preferred to ini files when it is lined up to each other.

INI files are not specified anywhere, so it ends up being a implementation-defined free-for-all. Also, YAML supports data structures that INI files don't. I don't understand the hate that YAML gets. If you're not tasked with writing a parser, the data format just works as expected.

> I don't understand the hate that YAML gets

https://noyaml.com/ is a decent overview of exactly how shit it is.

But outside of that, using spaces for logic is extremely error prone if you go past 10-15 lines and 2-3 levels deep.

Re: Quadlets might make me finally stop using docker-compose

#58

Post by memefrog »

hexo wrote: post #53
gigatexal wrote: post #35

Earlier quoted context omitted.

I mean the best part about open source and Linux is that you have choice. Do you want to run an OS devoid of SystemD? Fine. Will you be going against the tide and leaving a large part of the ecosystem behind? Yup. I’ve chosen to embrace systemd and learn it as it is the defacto standard it seems rather than fight what I think is a futile war against it. That being said. I won’t force you to use it if you don’t. But I…

systemd is extremely intrusive. anything dependent on it is a failure.

[dead]

Re: Quadlets might make me finally stop using docker-compose

#59

Post by [deleted] »

asabil wrote: post #28

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

[deleted]
Post reply on HN