SaaSHub helps you find the best software and product alternatives Learn more →
Docker-compose-stack Alternatives
Similar projects and alternatives to docker-compose-stack
-
Moby
The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
kubernetes-replicator
Kubernetes controller for synchronizing secrets & config maps across namespaces
-
trust-manager
trust-manager is an operator for distributing trust bundles across a Kubernetes cluster.
-
ca-injector
Painlessly use off-the-shelf images (and your own) in your k8s cluster, with custom root CAs.
docker-compose-stack reviews and mentions
-
What if your Pods need to trust self-signed certificates?
You're right, it's a little weird. I wrote a short essay about my setup[1] but the tl;dr is that I wanted certificates distributed in the same way every other thing on my machines is distributed.
I wanted my homeprod setup to be as hands off as possible while still allowing easy management. Each physical host is running Alpine. During provisioning I install docker, Tailscale, and manually start a "root" container that runs[2] docker compose and then starts a cron daemon. The compose commands include one or more "stack" files and are generated based on a yaml file listing the stacks for each host. Watchtower runs with a 30 second cycle time to keep everything updated, including the root container. Adding or updating services means committing and pushing a change to the root container repo, then CI builds and pushes a new image. Watchtower picks up the new image and restarts the root container, which re-runs Compose which in turn starts, stops, modifies, etc anything that's changed.
For certificates, I tried a number of different things but ultimately settled on the method I described earlier. The purpose of the container image is to 1) transport the certificates and install them in the right spot and 2) be updatable automatically with Watchtower.
Certificate changes are very similar to the root container, except the git repo self-modifies upon renewals (yes I keep private keys committed to git, it's a homelab, it's really not a big deal).
[1]: https://www.petekeen.net/homeprod-management-with-docker
[2]: https://github.com/peterkeen/docker-compose-stack/blob/main/...
-
Old School Linux Administration (My Next Homelab Generation)
I really like this article just for the straightforwardness of the setup. Pets not cattle should be the home server mantra.
My setup is not quite as simple. I have one homeprod server running Proxmox with a number of single task VMs and LXCs. A task, for my purposes, is a set of one or more related services. So I have an internal proxy VM that also runs my dashboard. I have a media VM that runs the *arrs. I have an LXC that runs Jellyfin (GPU pass through is easier with LXC). A VM running Home Assistant OS. Etcetera.
Most of these VMs are running Docker on top of Alpine and a silly container management scheme I've cooked up[1]. I've found this setup really easy to wrap my head around, vs docker swarm or k8s or what have you. I'm even in the process of stripping dokku out of my stack in favor of this setup.
[1]: https://github.com/peterkeen/docker-compose-stack
- docker-compose-stack: a fun little zero-ish dependency docker compose continuous deployment tool
- What is everyone using to deploy Docker?
-
A note from our sponsor - SaaSHub
www.saashub.com | 1 May 2024
Stats
peterkeen/docker-compose-stack is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of docker-compose-stack is Shell.
Sponsored