Migrating RomM
Migrating RomM to a new system
Migrating RomM to a new system is possible, but all of the docker volumes must be copied for RomM to run correctly.
Following the the setup in the Quick Start Guide these volumes are created be default
RomM should be stopped before following this guide.
volumes:
mysql_data:
romm_resources:
romm_redis_data:
services:
romm:
volumes:
- romm_resources
- romm_redis_data
romm-db:
volumes:
- mysql_data
These volumes will need to manually moved to the new system. This is a straightforward process that includes determining their location and then copying them.
Determining the docker root directory and copying the volumes
- First determine the docker root directory
The expected output on a standard linux system:
- Double check that the volumes have been created by docker and are owned by the docker engine
Following the default quick start guide the following volumes will have been made
- Inspect each volume to get the exact location of the volume data
- The output of the
docker inspect
will return the exact storage location of the volumes data
- Copy those volumes into a new location so that they can be safely migrated to a new system each volume needs to be in its own folder
cp -r /var/lib/docker/volumes/romm_mysql_data/_data/ /your/new/path/romm_mysql_data
cp -r /var/lib/docker/volumes/romm_romm_redis_data/_data /your/new/path/romm_romm_redis_data
cp -r /var/lib/docker/volumes/romm_romm_resources/_data /your/new/path/romm_romm_resources
- Update the
docker-compose.yml
volume paths with the newly copied data to determine RomM still loads correctly.
services:
romm:
volumes:
- /your/new/path/romm_romm_resources # romm_resources
- /your/new/path/romm_romm_redis_data # romm_redis_data
romm-db:
volumes:
- /your/new/path/romm_mysql_data # mysql_data
If RomM starts up correctly, then it is safe to copy all of your RomM folders to a new system.