this post was submitted on 26 Oct 2023
1 points (100.0% liked)

Self-Hosted Main

502 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

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

founded 1 year ago
MODERATORS
[email protected]
1
Migrating from ARM to X86 (alien.top)
submitted 11 months ago by [email protected] to c/[email protected]
13 comments fedilink hide all child comments
 

Hello All,

I currently have a home server on a raspberry pi 4 with all my services running as docker containers. All containers have their own directories containing the config and database files. This makes it easy to backup and export then.

​

However, in the future I have plans to migrate to a more powerful server. This means I will probably not be using a CPU with an ARM architecture. So effectively, I will also have to use the corresponding docker images. So will this new x86 docker image work with my backup docker config volumes?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 11 months ago (9 children)

These are containers not VMs. Just rebuild them. Rerun docker compose or docker run on the new machine

[–] [email protected] 1 points 11 months ago (2 children)

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?

[–] [email protected] 1 points 10 months ago

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.

load more comments (1 replies)
load more comments (7 replies)