absolutely.
IIRC about docker (correct me here as needed)
- you have a
/configpath. That’s the same as theLibrary/Application Supportfor the native. - You have that outside the container in the native FS?
- Make a tarball of it from outside the container (stopped of course and with the automatic stuff all turned off especially empty trash)
- Copy that into the VM .
You’re doing two things at the same time.
- cloning the host
- relocating the media
complete the steps for both (clone first) and it will fall in line.
Here’s the how-to’s to read and study. Hollar if you need more .
-
Backup/reload/clone the host from one (docker) to another (inside the VM)
Back up/ Restore /clone your PMS metadata -
This is the media relocation (changing mount points)
Moving your media and keeping the metadata - The TL;DR
Only ONE caution here.
Cloning is a perfect clone (copy). The server ID numbers as well. You’ll get a collision if both come online at the same tine. At some point, the MachineID, ProcessedMachineID and AnonymnousMachineID values in Preferences.xml will need be removed so new can be generated (in the new VM / host). It’ll save the other credentials but separate the otherwise identical twins.
If you think about this, you could stand up the new machine in the VM then take it live on the Hosted machine after you’ve gotten it all perfected.
