I read every word of your screed. You are advocating for an Easy Button. You don’t have any details how it will work or why, you just want everyone else to change how they do things to your vague and unspecified plan for an Easy Button.

I’m working to build an open platform…

My bad, why didn’t you link your repo from the start? Then we could have a productive discussion about your design docs and the initial code for your new OS.

Since it has what you want, why don’t you use Windows in that case?

As a lot of you already know, backward compatibility has never really been the strong suit of Linux or the BSDs.

From the first sentence I have the strong impression the author is deeply confused and mistaken.

weirdly i just block them all

At lot of it comes down to attitude. I remember a coach I heard responding to someone who said “I find it impossible to get out of bed when my alarm goes off. All I want to do is hit the snooze” and the coach said something like this, “Really? All it takes to get out of bed when your alarm goes off is to put your feet on the floor and stand up. If you woke up completely tired in the middle of the night but your bed was on fire I bet you would have no problem getting right out. That means you can easily get out of bed as soon as you decide its what you need to do. Decide the night before, when that alarm goes off in the morning you will put your feet on the floor and stand right up.”

yeah linux is completely unusable bro /s

I got in the car headed for work, turned on the radio for the morning news and they were talking about it having just happened about 20 min earlier. I didn’t know what to think.

Right as I got to work a bunch of people were heading to the red cross to donate blood so I went with them.

my dog book says to pull fighting dogs apart by grabbing by the base of their tail

I don’t know. I’m having great difficulty finding an Ask comm where people ask sincere questions that can’t be answered with a simple search.

We need it brother. Seeing you succeeding and posting daily is one of the few rays of hope for me that I will be able to get myself back on track.

Breaking up always sucks if you really care about the other person but for reasons can’t stay in a relationship with them. The best advice I ever got was that if you have your reasons for why you need to get out of a relationship, that’s all that matters. The person who doesn’t want to break up will always have their reasons why they want to stay together. For a relationship to work, both people need strong reasons to stay together. It can’t be just one of them.

I use ssh and the built in socks proxy for that ssh -D 1080 some_server will connect to the server and open a socks port on your local 1080 that exits via the server’s IP.

Honest question

yes exactly how i start my real tech questions

The usage is simple. If you name a quadlet (or systemd service unit file) with an @ in it then you can use it. Like foo@.container then anything you put between the @ and . is passed into the resulting unit file as %i.

So systemctl start foo@bar.service will pass ‘bar’ in where %i exists in the unit file. From there you can use it in a StartPreExec or whatever else to do instance specific stuff when the instance of the containerized service start.

Like ExecStartPre=/usr/local/bin/activate_config %i for example. A contrived example but hopefully you get the idea: with one quadlet file and a little scripting you can start many instances of a service that each automatically pull in their own configs.

I agree that ergonomics are also important, but for me not the top priority for me. For Podman, I like the way I can use Quadlet to quickly deploy and run containerized stuff.

However I really like it for building and running my own app stack pods. The combination of Quadlet and SystemD instance aliases is very powerful. I use this to drive all kinds of configuration automation.

Sounds like you are more interested in how the “house” was painted while I’m more focused on the construction materials and architecture.

If you truly don’t care what the source code looks like or how it works internally, then we aren’t even having the same conversation.

What do you mean by “clean design”?

If you are comfortable reading the source code for each project that is the most revealing way to see the difference.

In short, Docker has a lot more code because it duplicates a lot of kernel and systemd functionality (often poorly), uses multiple components that communication over grpc with each other to do things, requires setuid binaries, and defaults to running everything as root.

Podman, is a straight forward clean simple program that fully uses kernel and systemd interfaces rather than duplicating functionality. Quadlet is build on systemd generators and its use of templates via systemd instances lets you use deterministic dynamic configuration in ways that is unlike anything in Docker.

I think its more than Compose does a small subset of what Quadlets can do. I can understand why if your only use case is Compose and you already like it, why change? For me, the rootless by default and daemonless nature of podman quadlets, and its clean design all make it the preferred choice.

I don’t know how you would even compare them. Quadlets can do what Docker Swarm or Kube does with dynamic instances and dependency lifecycle management. Docker Compose doesn’t have nearly the same features as Podman Quadlet.