{"full_name":"psviderski/uncloud","owner":"psviderski","name":"uncloud","shard":"1","url":"https://github.com/psviderski/uncloud","description":"A lightweight tool for deploying and managing containerised applications across a network of Docker hosts. Bridging the gap between Docker and Kubernetes ✨","homepage":"https://uncloud.run","topics":["containers","docker","docker-compose","golang","orchestration","self-hosted","devops","kubernetes","deployment","uncloud"],"tag_pages":["containers","deployment","devops","docker","docker-compose","golang","kubernetes","orchestration","self-hosted"],"language":"Go","license":"Apache-2.0","avatar":"https://avatars.githubusercontent.com/u/783910?u=453f9b7df638dcb6abefb8e8f37aef475ce71ef8&v=4","created_at":"2024-07-20T11:13:36Z","pushed_at":"2026-11-06T11:22:23Z","metrics":{"stars":5615,"forks":184,"watchers":22,"issues":236,"prs":187,"releases":37,"issues_open":72,"issues_closed":164,"prs_open":19,"prs_closed":56,"prs_merged":112,"discussions":30},"growth":{"day":{"stars":1,"forks":0,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[5605,5608,5612,5612,5612,5614,5615],"forks":[184,184,184,184,184,184,184],"watchers":[null,22,22,22,22,22,22],"issues_open":[null,72,72,72,72,72,72],"prs_open":[null,17,18,18,18,18,19]},"boards":{},"same_owner":[],"issues":[{"number":172,"title":"Update Corrosion to the latest version from upstream","comments":23,"created_at":"2025-11-07T02:56:54Z"},{"number":369,"title":"uc down or uc undeploy would be nice","comments":20,"created_at":"2026-05-16T17:19:22Z"},{"number":209,"title":"Provide windows CLI with scoop","comments":14,"created_at":"2025-12-07T15:08:06Z"},{"number":425,"title":"Simplify SSH tunnel for better security","comments":11,"created_at":"2026-08-20T23:29:44Z"},{"number":126,"title":"Feature request: IPv6 support on Uncloud network","comments":10,"created_at":"2025-09-17T21:38:18Z"},{"number":439,"title":"feat: volume copying","comments":7,"created_at":"2026-10-07T05:39:22Z"},{"number":348,"title":"allow `!machine` in x-machines?","comments":7,"created_at":"2026-05-02T05:40:07Z"},{"number":227,"title":"[BUG] Support for Amazon Linux 2023 (GLIBC 2.34)","comments":7,"created_at":"2025-12-25T05:01:29Z"}],"discussions":[{"number":322,"title":"Initialise a cluster from the machine itself","comments":0,"category":"Ideas","created_at":"2026-04-21T09:12:31Z"},{"number":280,"title":"Caddy L4 for TCP / UDP passthrough and SNI proxy","comments":4,"category":"Ideas","created_at":"2026-03-20T08:55:09Z"},{"number":271,"title":"sudo/root only needed for `uc machine init`?","comments":1,"category":"Q&A","created_at":"2026-03-16T10:48:24Z"},{"number":268,"title":"Multi tenant","comments":4,"category":"Q&A","created_at":"2026-03-12T14:42:04Z"},{"number":289,"title":"Add safeguards when multiple contexts are available","comments":11,"category":"Ideas","created_at":"2026-03-08T01:20:01Z"},{"number":255,"title":"Co-op Cloud & Uncloud","comments":1,"category":"General","created_at":"2026-02-16T22:58:56Z"},{"number":249,"title":"Labels instead of extensions","comments":1,"category":"Ideas","created_at":"2026-01-30T11:40:11Z"},{"number":241,"title":"Is this an alternative to fly.io and dokploy ?","comments":1,"category":"Q&A","created_at":"2026-01-08T08:26:06Z"}],"latest_release":{"name":"v0.22.0","tag":"v0.22.0","published_at":"2026-11-06T10:48:11Z","body":"This release makes **cluster storage for Caddy the default**, adds **service and container labels**, a new **`uc service update`** command to change a service without recreating its containers, **`uc image rm`** to clean up images across machines, and **DNS names for machines**. It also brings fixes for logs, faster stop-first deployments, and a much calmer daemon on busy clusters.\r\n\r\n## ⚠️ Heads-up before upgrading\r\n\r\n- `uc caddy deploy` now deploys the Uncloud Caddy image with cluster storage ([22b1c68](https://github.com/psviderski/uncloud/commit/22b1c68)). Upgrading Uncloud doesn't touch your running Caddy. But the next `uc caddy deploy` switches it to the new image and storage. Caddy doesn't copy certificates between storage backends, so it will reissue them unless you migrate them first. Read [Upgrading from earlier versions](https://uncloud.run/docs/concepts/ingress/cluster-storage-for-caddy#upgrading-from-earlier-versions) before you redeploy Caddy.\r\n- `uc caddy deploy` requires the 0.22.0 daemon on all machines. Upgrade the daemons first.\r\n- Machine names must be valid DNS labels ([ce1c6bd](https://github.com/psviderski/uncloud/commit/ce1c6bd)). This means lowercase letters, numbers, and hyphens, up to 63 characters. The names `rr` and `nearest` are reserved, and a name can't look like a machine ID. This applies when you add or rename a machine.\r\n\r\n## Cluster storage for Caddy by default\r\n\r\nChange: [22b1c68](https://github.com/psviderski/uncloud/commit/22b1c68), docs: [Managing Caddy](https://uncloud.run/docs/concepts/ingress/managing-caddy)\r\n\r\nIn v0.21.0, we added an opt-in [cluster storage](https://uncloud.run/docs/concepts/ingress/cluster-storage-for-caddy) for Caddy to share TLS certificates across machines. Now it's the default.\r\n\r\nNew clusters and `uc caddy deploy` now use the Uncloud Caddy image [`ghcr.io/unlabs-dev/caddy-uncloud`](https://github.com/unlabs-dev/caddy-uncloud/pkgs/container/caddy-uncloud). It's a Caddy build with the Uncloud storage module and a few popular modules, such as [caddy-l4](https://github.com/mholt/caddy-l4) and [cloudflare](https://github.com/caddy-dns/cloudflare) for DNS challenges. So you can get a wildcard certificate with Cloudflare without building your own image.\r\n\r\n`uc caddy deploy` also remembers the `--image`, `--caddyfile`, and `--machine` values you passed. You no longer need to repeat them every time you upgrade Caddy. Pass an empty value to reset a flag to its default:\r\n\r\n```shell\r\n# Deploy with a custom global config only on two machines.\r\nuc caddy deploy --caddyfile global.Caddyfile --machine machine1,machine2\r\n\r\n# Later, upgrade Caddy to the latest image. The custom config and machines are kept.\r\nuc caddy deploy\r\n\r\n# Go back to the default global config and deploy to all machines.\r\nuc caddy deploy --caddyfile \"\" --machine \"\"\r\n```\r\n\r\nIf you have an existing cluster, follow [Upgrading from earlier versions](https://uncloud.run/docs/concepts/ingress/cluster-storage-for-caddy#upgrading-from-earlier-versions). It explains how to keep your certificates when switching to cluster storage, including for Caddy managed with Compose.\r\n\r\n## Service and container labels\r\n\r\nChanges: [81f30aa](https://github.com/psviderski/uncloud/commit/81f30aa), [c1a7f84](https://github.com/psviderski/uncloud/commit/c1a7f84), [7b48ac5](https://github.com/psviderski/uncloud/commit/7b48ac5)\r\n\r\nYou can now set labels in Compose. Uncloud supports both kinds of labels:\r\n\r\n- `labels` sets Docker labels on containers, for tools like backup agents, log shippers, or monitoring agents.\r\n- `deploy.labels` sets service labels. They're stored with the service but not applied to containers. Use them for metadata about the service itself. Uncloud already uses them, for example, to mark the Caddy service managed by `uc caddy deploy`.\r\n\r\n```yaml\r\nservices:\r\n  db:\r\n    image: postgres:18\r\n    labels:\r\n      docker-volume-backup.stop-during-backup: \"true\"\r\n    deploy:\r\n      labels:\r\n        owner: alice@example.com\r","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}