Self Hosted - Self-hosting your services.

17149 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.

Rules

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

Important

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate. This is strongly encouraged!

Cross-posting

!everything_git@lemmy.ml is allowed!
!docker@lemmy.ml is allowed!
!portainer@lemmy.ml is allowed!
!fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
!selfhosted@lemmy.ml is allowed!

If you see a rule-breaker please DM the mods!

founded 4 years ago

MODERATORS

Zoe8338@lemmy.ml

dogmuffins@lemmy.ml

testman@lemmy.ml

Moving docker image data between VMs (lemmy.ml)

submitted 2 months ago by trilobite@lemmy.ml to c/selfhost@lemmy.ml

11 comments fedilink hide all child comments

I have 2 servers both running a Debian VM each. The old VM was one of the first o installed several years ago when I knew lityle and its messed up and has little space left. It running on Truenas Scale and has a couple of docker apps that I'm very dependent on (Firefly, Hammond). I want to move the datasets for these docker apps to a newer VM running on Proxmox server. It a Debian 13 VM with loads of space. What are my options for moving the data given neither Firefly nor Hammond have the appropriate export / import functions? I could migrate the old VM that that wouldn't resolve my space issue. Plus it Debian 10 and it would take a lot to being it up to Trixie.

you are viewing a single comment's thread
view the rest of the comments

[–] just_another_person@lemmy.world 6 points 2 months ago (1 children)

The first rule of containers is that you do not store any data in containers.

The second rule of containers is that you run them from a versioned config with proper volumes and tagging. Always.

If you obey these rules, then it's as simple as moving the volumes to another host and starting your containers. They're fully portable that way.

[–] trilobite@lemmy.ml 3 points 2 months ago

The first rule of containers is that you do not store any data in containers.

Do you mean they should be bind mounts? From here, a bind mount should look like this:

version: '3.8'

services: my_container: image: my_image:latest volumes: - /path/on/host:/path/in/container

So referring to my Firefly compose above, then I shoudl simply be able to copy over the /var/www/html/storage/upload for the main app data and the database stored in here /var/lib/mysql can just be copied over? but then why does my local folder not have any strorage/upload folders?

user@vm101:/var/www/html$ ls index.html