GuidesProduction setup
Upgrade Ferry
Replace the two binaries and restart the unit. Your containers continue to run during the restart.
Before the upgrade, the proxy of ferryd sends the public traffic to your containers.
1 / 3
Replace the binaries
Replace the two binaries in /usr/local/bin. Use the same command as for the first install.
sudo install -m 755 ferryd ferry /usr/local/bin/Restart the unit
sudo systemctl restart ferrydDeploys in progress fail
A deploy that is in progress at the moment of the restart gets a failed status. See Self-healing.
- The containers that run continue without limits until Ferry replaces them. Deploys, restarts, the reconciler and job runs start new containers with limits: the limits of the service, or the defaults of the server.
ferry restart NAMEgives a service its limits without a build. - A datastore from before the upgrade runs without limits until you change its limits or Ferry creates its container again.
ferry db update NAME --memory defaultapplies the server defaults in place. - Before, Ferry ignored
plan:in arender.yaml. Now the first apply of such a file restarts the live services whoseplan:sets their limits, without a build. It also applies the plans of its databases and key value stores to their containers in place. - With the default memory, the kernel stops an app or a database that needs more. First give it its own limit (
ferry update NAME --memory 2G,ferry db update NAME --memory 2G), or raise--default-memory-limit.