[dead]
Quadlets might make me finally stop using docker-compose
11–20 of 212 posts
Re: Quadlets might make me finally stop using docker-compose
#12Say 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 also miss the simplicity of compose, but for me running rootless is worth the tradeoff. It also forced me to rethink how I used containers and I realized many times a simple podman_run.sh is enough. It also helped me understand containers better because there was less magic going on, sometimes limitations can be good.
Re: Quadlets might make me finally stop using docker-compose
#13Say 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
It is not entirely obvious - can I use quadlets in an ad-hoc fashion to spin up a project? The example makes it seem like it is exclusively for long running services.
Re: Quadlets might make me finally stop using docker-compose
#14Say 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
[deleted]
Re: Quadlets might make me finally stop using docker-compose
#15> However, as with watchtower, that’s another external dependency. Docker compose is part of docker now, it's just another subcommand.
[deleted]
Re: Quadlets might make me finally stop using docker-compose
#16Nitpick 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.
Re: Quadlets might make me finally stop using docker-compose
#17Nitpick 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.
It's not type safe.
Re: Quadlets might make me finally stop using docker-compose
#18Say 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 also miss the simplicity of compose, but for me running rootless is worth the tradeoff. It also forced me to rethink how I used containers and I realized many times a simple podman_run.sh is enough. It also helped me understand containers better because there was less magic going on, sometimes limitations can be good.
> I also miss the simplicity of compose, but for me running rootless is worth the tradeoff.
To setup/tear down software dev environments deployed locally, the root/rootless discussion isn't really relevant. Ease of deployment and ease of use are critical though, and Docker is above all a development experience victory.
Re: Quadlets might make me finally stop using docker-compose
#19Earlier quoted context omitted.
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.
It's not type safe.
> It's not type safe.
I fail to see what leads you to believe this is a relevant point when discussing INI files as the alternative to YAML.
Re: Quadlets might make me finally stop using docker-compose
#20Why 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?