process-compose VS podman-compose

The IMO superior https://github.com/F1bonacc1/process-compose project has this built in, while allowing to manage regular programs that don't require containers.

See:

Devbox can also run services too. Both products use an awesome process runner called process-compose (https://github.com/f1bonacc1/process-compose/) which is worth checking out (it's even built with nix!)

I've been using https://github.com/F1bonacc1/process-compose with great success.

It's a userspace process compositor that works across all relevant platforms, supporting daemon processes and k8s style readiness/health checks.

In combination with nix flakes, it quickly reduced my projects docker-compose usage for easy-to-configure services.

This gave huge performance benefits for the M1 Mac folks on my team especially for CPU intensive processes thanks to native binaries.

For maximal ease of use, the remaining docker-compose containers are started/stopped as a process-compose task.

In order to run a simple client-server (1 client, 5 servers) application, I wrote a simple docker-compose file and everything worked great. My dev flow would be the usual: make some changes/optimizations, spin everything up, run a bunch of tests, and go back to step one. At some point, I felt that for my dev environment and language (Linux, golang). docker-compose is great for spinning everything up, but for rapid development, it actually slows me down. I didn't really need containers. I tried to find an alternative solution. Something like a docker-compose, but for native processes, but most of the tools that I found were CI/CD oriented. I like K9S (who doesn't?) and I like docker-compose (some don't), so I built a Frankenstein Monster of them both :) https://github.com/F1bonacc1/process-compose I am not sure if you'll find it as useful as I do, but in any case, any feedback is more than welcome.

Podman (via podman-compose),

Source code for the feature is here if you care to inspect it:

https://github.com/containers/podman-compose/blob/bce40c2db3...

Admittedly, I'm still on podman 4.3.1, but I dont' see any reason why this would stop working in later versions of podman.

Can someone link me to what Compose means in this context? Google takes me to https://github.com/containers/podman-compose but I just wanna make sure that's what they are talking about.

🛑 Docker Desktop is free for personal use but requires a paid subscription for enterprises. A free open source alternative is Podman and Podman Compose which uses the same core syntax as the Docker tools and can be used as a near drop-in replacement.

I’m dumb. When I wrote the article it was late. Docker-Compose really was a game changer.

Yea Podman compose exists. I’ll add a section about docker compose to it in an update.

https://github.com/containers/podman-compose

From googling this error I've come across a few different threads but I haven't gained any success. Firstly I found this github thread which doesn't reference my error but still seems related. I followed the "sudo podman-compose systemd --action create-unit" and "podman-compose systemd -a register -f myfile.yml" minus the -f flag as it wouldnt run with that. This indeed created a [email protected] file, but its created in the /etc/systemd/user directory rather than /etc/systemd/system which raises an issue as I'm having to run these two containers as root. I try registering the podman-compose@torrent but I'm told the service doesnt exist. Running it as user I'm told it failed to connect to bus: no medium found. So I basically reached a dead end there.

Have a look at Podman Compose

You can also use podman-compose for the orchestration https://github.com/containers/podman-compose