What's new
Force service redeployment
Added --recreate flag to the deploy command to force container recreation even if their configuration and image haven't changed. This is particularly useful when you've pushed updated images directly to machines using tools like unregistry, and need to redeploy services to use the updated images without changing their tags. Or just want to test the redeployment process without changing the service configuration.
Reset machine on initialisation
machine init and machine add commands now ask you whether to reset the machine if they detect that the machine is already a cluster member. This helps when:
- Repurposing a machine that was previously part of a different Uncloud cluster
- Recovering from a failed or incomplete previous installation
- Starting fresh after testing or experimentation with Uncloud
Default restart policy
Changed the default restart policy for service containers from always to unless-stopped. This allows you to stop containers manually and have them remain stopped even after a system reboot or Docker restart.
Upgrade to 0.11.0
Uncloud CLI locally
To upgrade the Uncloud CLI (uc) locally:
# Homebrew (macOS, Linux)
brew upgrade uncloud
# Install script (macOS, Linux)
curl -fsS https://get.uncloud.run/install.sh | shMachine daemon
To upgrade the Uncloud daemon on your machines, run the following commands on each machine:
# AMD64
curl -fsSL -o uncloudd.tar.gz https://github.com/psviderski/uncloud/releases/download/v0.11.0/uncloudd_linux_amd64.tar.gz
# ARM64
# curl -fsSL -o uncloudd.tar.gz https://github.com/psviderski/uncloud/releases/download/v0.11.0/uncloudd_linux_arm64.tar.gz
tar -xf uncloudd.tar.gz
sudo install uncloudd /usr/local/bin/uncloudd
rm uncloudd uncloudd.tar.gz
sudo systemctl restart uncloud