Self-Hosted Main

511 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

[email protected]

Migrating from ARM to X86 (alien.top)

submitted 1 year 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 1 year 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 1 year 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] 2 points 1 year ago

It should, in theory, only the binaries should be different so all config/media should work.

load more comments (1 replies)

load more comments (7 replies)