Hacker News new | ask | show | jobs
by cpitman 1210 days ago
This looks quite nice. I run a server which is already RHEL+podman+generated systemd units, but this both simpler and more declarative/idempotent than my current setup. Anything that helps convince people that containers running on a single server can be simple, and doesn't require an entire k8s stack.
2 comments
creshal 1209 days ago
It's interesting that Redhat promotes this, despite having already invested quite a lot into systemd-nspawn for roughly the same purpose. Between it and lxd there's already some options for these sorts of simple, single-host container runtimes.
link
mytailorisrich 1209 days ago
Podman is also Red Hat do they win either way.

Anyway, I think that Podman is the mature Docker and tries to fit much better into the linux/unix-y way of doing things. Especially, being daemonless allows to integrate into systemd, etc. the way it should, and makes for a mature integration of containers into the ecosystem.

link
theteapot 1209 days ago
> Anything that helps convince people that containers running on a single server can be simple, and doesn't require an entire k8s stack.

Docker?

link
IceWreck 1209 days ago
Docker compose isn't exactly meant for production
link
dusanh 1209 days ago
The company I used to work for, used docker-compose to serve its SaaS product to 100+ clients. I wasn't part of that team, but it seemed to me they were quite happy with it.
link
KronisLV 1209 days ago
Can second this: I've seen companies that wanted the benefits of containers but didn't need orchestration yet do just fine with Docker Compose in prod.

Of course, when orchestration became a necessity, almost everyone looked in the direction of Kubernetes, as opposed to something like Nomad or Swarm, probably due to its popularity.

link
theteapot 1209 days ago
Other comments. You can also use docker-swarm with just a single master node.
link
jpitz 1209 days ago
tl;dr it wasn't before, but now it is.

It is true that there once was a disclaimer on the compose homepage that stated that the product was not recommended for production workloads.

Given that disclaimer no longer exists, along with the existence of [1], leads me to advocate using it in production.

[1] https://docs.docker.com/compose/production/

link