Question Docker migration to new NAS

[Rusty]

Well said @one-eyed-king !

but is apparently too complicated

 

[alfabravo]

@one-eyed-king
will do and report next week when new DS has arrived. Now i'm preparing and gathering information.

 

[alfabravo]

Hi, as promised my experience with migration to a new NAS.
It was easier as i've expected and without SSH.
My approach(old DS218+, new DS718+):
1. installed docker on 718
2. installed all my containers (actually only downloaded then from repo) on 718.
3. copied the whole folder /volume1/docker to 718
4.export settings for all containers from 218.
5.import settings on 718.
6. run containers.
I've moved Docker with all my container (bitwardenrs server, homebridge,deconz,
phihole, transmissio) without any issue.
Only portainer didn't work.

Failure
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

i don't know why he can't find docker.socket and how to fix it. Maybe a new installation will help.

Thank again for everyone. I hope it will help other users.
regards

 

[Rusty]

You need to run that portainer container via ssh because of docker.sock parameter that needs to be mounted

 

[alfabravo]

@Rusty
now i have no issues!
Thank you

 

[one-eyed-king]

Hi, as promised my experience with migration to a new NAS.
It was easier as i've expected and without SSH.
My approach(old DS218+, new DS718+):
1. installed docker on 718
2. installed all my containers (actually only downloaded then from repo) on 718.
3. copied the whole folder /volume1/docker to 718
4.export settings for all containers from 218.
5.import settings on 718.
6. run containers.
I've moved Docker with all my container (bitwardenrs server, homebridge,deconz,
phihole, transmissio) without any issue.
Only portainer didn't work.
Code:

So you didn't move from ext4 to btrfs... that made things way easier.
Configuration and data inside the containers are still there?

 

[alfabravo]

yes, i did. i moved from ext4 to btrfs and kept everything.

 

[one-eyed-king]

Not sure what to think of this... as long as things work well... why not.

 

[alfabravo]

Not sure what to think of this... as long as things work well... why not.

magic

 

[one-eyed-king]

Any idea which storage driver the docker packes uses on your new ds?
Did you check docker info | grep Storage (as root) to see which one is used.

Maybee somehow you managed to backup and restore the dockerd.json file.

 

[alfabravo]

Did you check docker info | grep Storage (as root) to see which one is used.

docker info | grep Storage
Storage Driver: btrfs
WARNING: No kernel memory limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support

# docker info
Containers: 13
 Running: 12
 Paused: 0
 Stopped: 1
Images: 6
Server Version: 18.09.6
Storage Driver: btrfs
Logging Driver: db
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs db fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 0cf16177dbb234350dc27dd2bbd1d7cebd098108
runc version: 6cc9d3f2cd512eeb3d548e2f6b75bcdebc779d4d
init version: e01de58 (expected: fec3683)
Security Options:
 apparmor
Kernel Version: 4.4.59+
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 9.577GiB
Name: HOME-NAS
ID: VJUX:B7MQ:MFGI:KPNU:TJVI:JMK6:LLX6:F2GU:V3NZ:FSEJ:5JAW:7EA7
Docker Root Dir: /volume1/@docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No kernel memory limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support

i really didn't do anything else but only the steps described. I'm not very good in SSH.
i'm really happy that its worked out and all my smart home is still running.

 

[one-eyed-king]

Thank's for sharing.

In germany we have a saying: "everyone said: it's impossible. Then someone came along who didn't knew that (it's impossible) and just did it".

Knowing you migrated from aufs to btrfs and everything continues to work either means you re-created everything with the other actions in your migration OR Docker (or Syno) actualy implemented a migration when the storage driver is changed.

I can finally find peace with "it's magic".

 

[jeyare]

Great use-case. Gents, what about prepare a clean Resource for such general migration? Thx.

 

[bjorna]

Hi, slightly different situation, I am considering retiring my DS713+ and moving to a new DS720+. Since the two drives are in good shape, I am thinking about just moving them to the 720. Since my main usage of the NAS is through Docker containers, I am wondering whether they will work "out of the box" after moving to the new NAS? Or must I go through some of the steps discussed in this thread to export/import them?

 

[Rusty]

Hi, slightly different situation, I am considering retiring my DS713+ and moving to a new DS720+. Since the two drives are in good shape, I am thinking about just moving them to the 720. Since my main usage of the NAS is through Docker containers, I am wondering whether they will work "out of the box" after moving to the new NAS? Or must I go through some of the steps discussed in this thread to export/import them?

would be good to have some backup of the whole setup, but 99% all will be running just fine out of the box. I have done many of those migrations and there shouldn't be any problems at all.