- Getting Started Configuration Accessing Your Cluster Hypervisors Maintenance Hook Scripts Troubleshooting
On this Page:
Migrating or restoring croit container
Sometimes, you want to migrate the croit container to a different host, or the current host is not available anymore, and a redeployment of the container is needed.
If the container is healthy (you want to voluntarily migrate it, and no crash happened), make a backup of your current configuration using your preferred method (cloud or local):
Backups view (Croit->Backups)
In the new host, pull and run a new docker container using the same version you had in the previous one:
docker create --name croit-data croit/croit:latest
docker run --cap-add=SYS_TIME -v /var/run/docker.sock:/var/run/docker.sock --net=host --restart=always --volumes-from croit-data --name croit -d croit/croit:latest
The important match should be the ceph version, please use the proper tag croit/croit:latest.<ceph version>
if you are not running the latest ceph version yet.
From the UI in the new container, restore the backup using the same method you chose before:
Restoring Backup view
Optional
If you plan to use a different IP address for the new host, server, or virtual machine, you will need to update the new IP address in the configuration settings (Config → Networks → Boot IP). After making this change, reboot each node one by one via SSH. This will ensure they pick up the new management node IP through the kernel command line.
Fixing Boot IP view (Config → Networks → Boot IP)