You’ll have to make sure the volumes are mapped to appropriate directories. Such that if on your pi setup its /somedir/app1/blah, that you change it to /newdir/app1/blah.
It’s even easier if you re-create the same directory heirarchy on the new server, and you can rsync your folders over. I found it easier to re-create the containers first, and all my volume mounts are bind type: ie use an existing folder, rather than letting docker create the volume wherever it wants.
I did exactly this kind of migration not that long ago, and for the same reason, and from the same source/destination platforms.
You’ll have to make sure the volumes are mapped to appropriate directories. Such that if on your pi setup its
/somedir/app1/blah, that you change it to/newdir/app1/blah.It’s even easier if you re-create the same directory heirarchy on the new server, and you can rsync your folders over. I found it easier to re-create the containers first, and all my volume mounts are
bindtype: ie use an existing folder, rather than letting docker create the volume wherever it wants.I did exactly this kind of migration not that long ago, and for the same reason, and from the same source/destination platforms.