|
|
|
|
|
by 9dev
1014 days ago
|
|
Using Docker Compose with Podman: https://www.redhat.com/sysadmin/podman-docker-compose
Using containerd: https://github.com/mc256/containerd-compose
Using nerdctl: https://github.com/containerd/nerdctl I'd really disagree that compose files are somehow one-shot, or blindly modified. To the contrary, really, we have them checked in with the source code. Upon deployment to the cluster, the (running) services will be intelligently updated or replaced (in a rolling manner, causing zero downtime). LXC might be more elegant, but I have no idea what simple, file-based format I could use to let engineers describe the environment their app should run in without compose. I need something that even junior devs can start up with a single command, that can be placed in the VCS along with the code, and that will not require deep Linux knowledge to get running. Open for suggestions here, really. |
|