uncloud

Looks like uncloud has no control plane, just a CLI: https://github.com/psviderski/uncloud#-features

I got tired of the push-to-registry/pull-from-registry dance every time I needed to deploy a Docker image. In certain cases, using a full-fledged external (or even local) registry is annoying overhead. And if you think about it, there's already a form of registry present on any of your Docker-enabled hosts — the Docker's own image storage. So I built Unregistry [1] that exposes Docker's (containerd) image storage through a standard registry API. It adds a `docker pussh` command that pushes images directly to remote Docker daemons over SSH. It transfers only the missing layers, making it fast and efficient. docker pussh myapp:latest user@server Under the hood, it starts a temporary unregistry container on the remote host, pushes to it through an SSH tunnel, and cleans up when done. I've built it as a byproduct while working on Uncloud [

I'm actually building something in between Docker and Kubernetes: https://github.com/psviderski/uncloud. Like you I wanted that middle ground without the operational overhead. It's basically Docker-like CLI and Docker Compose with multi-machine and production capabilities but no control plane to maintain. Still in active development but the goal is to keep it simple enough that you can easily understand what's happening at each layer and can troubleshoot.