Hacker News Reader

Comment by traverseda | Hacker News Reader

Why would you want to use this over one of the official docker compose setups? https://github.com/paperless-ngx/paperless-ngx/blob/main/doc...

They will also automatically launch if you have docker running at boot. Is it just because you prefer redhat/IBM's docker equivalent stack to the much more common and cross platform docker install?

View on HN

I would want this over docker and docker-compose any day.

I've been using docker compose in production for a couple of years now and it adds another layer on top of systemd that is a continuous source of headache, especially during updates.

Podman gets it right: no central daemon, can automatically generate systemd services for a whole pod. Updates are seamless.

This by itself is enough of a reason to me.

Seconded on the things Podman gets right. Also the isolation of all of the containers in their own network name space makes port management on my workstation super easy. I run many things like Paperless NGX using the same pattern in the start.sh file of my little project. I then use Traefik to route traffic to the right pod. It works great.

I don't use Docker at all on any of my infra or workstations. That's why I made this.

Alright, but you've sort of re-invented docker compose there, but as a shell script. These days docker compose even work with podman if you really prefer IBM's docker implementation to the original.

I am well aware that docker compose works mostly with Podman. I prefer to use Podamn with systemd over it. I have you even tried giving this a shot? Maybe give using Podman + systemd following my example in Bash instead of Docker + Docker Compose and you will see why?

Well... Maybe re-inventing was part of the fun or a learning experience. If you want, there is even this: https://github.com/Mitigram/docker-compose-build

Reply on news.ycombinator.com