3 ms·
Compose is great, but a couple things always created friction for me when using it for non-local setups: * Lack of a user-friendly way of managing a Docker Com
by tontony 5mo ago
Compose is great, but a couple things always created friction for me when using it for non-local setups:
* Lack of a user-friendly way of managing a Docker Compose installation on a remote host. SSH-forwarding the docker socket is an option, but needs wrappers and discipline.
* Growing beyond one host (and not switching to something like Kubernetes) would normally mean migrating to Swarm, which is its own can of worms.
* Boilerplate needed to expose your services with TLS
Uncloud [1] fixed all those issues for me and is (mostly) Compose-compatible.
[1] https://github.com/psviderski/uncloud/ https://github.com/psviderski/uncloud/
- esperent 5mo ago> Lack of a user-friendly way of managing a Docker Compose installation on a remote host I've been using portainer for years, it's decent.
- chatmasta 5mo agoFor remote installation, use the `docker context` command. You create a context with a named SSH host and then it connects via SSH to that host (as configured in your local ssh_config) and uses its docker daemon. Everything works flawlessly apart from local bind mounts (for obvious reasons). If you remember `docker machine`, this is basically the modern version of that.
- tontony 5mo agoThat's fair; good solution.
- deleted 5mo ago[deleted]