1
Migrating from ARM to X86
(alien.top)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Oct 2023
1 points (100.0% liked)
Self-Hosted Main
504 readers
1 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
For Example
- Service: Dropbox - Alternative: Nextcloud
- Service: Google Reader - Alternative: Tiny Tiny RSS
- Service: Blogger - Alternative: WordPress
We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.
Useful Lists
- Awesome-Selfhosted List of Software
- Awesome-Sysadmin List of Software
founded 1 year ago
MODERATORS
These are containers not VMs. Just rebuild them. Rerun docker compose or docker run on the new machine
Yes, I know that. I am just curious if the files containing the data of previous images will work with the new images as well?
It should, in theory, only the binaries should be different so all config/media should work.
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.