Move docker containers to a new volume on Synology NAS

A while ago I made a video on how to create a storage pool on M.2 NVMe's which you have in those slots in your Synology. Check that video here:
www.vikash.nl/...
In this video, I will show you how to move your docker containers to that new volume, take advantage of those M.2 NVMe's performance, and keep all the persistent data and configuration.

[@danelfring5037]

resetting the container is easier instead of manually mapping after the Volume move, great video thx!

[@buleini]

Happy to have found this video, this ''trick' also works on the DSM 6 version of the Docker package. Just carefully reselect the paths on the new volume and type in the mountpoints. Thanks for sharing

[@thaitichi]

Took me a while to find this video. Exactly what I needed. Thank you!!!

[@av1155G]

Thank you for the guide. I followed the steps, and while they worked, I noticed that writes were still occurring on the old volume for some reason. To resolve this, I took additional steps beyond the video's instructions. After implementing the process outlined in the video, the containers now reference the new SSD volume, and the shared folder has been successfully transferred. However, to ensure that all writes were directed to the new volume, I took the extra step of uninstalling and then reinstalling Container Manager on the new SSD volume. Please note that uninstalling Container Manager will remove your containers, necessitating a rebuild. But don't worry - because the shared Docker folder has been moved, your data remains intact. Rebuilding the containers should be straightforward. You can use the same docker-compose file to rebuild your projects or rerun any task scheduler scripts you have for container installation. Remember, network configurations, such as MacVLAN, will be deleted, so you'll need to recreate them after reinstalling Container Manager before you can reinstall your containers. After these steps, I confirmed that all write operations are now directed to the new SSD volume, ensuring that the shared folder is also correctly located on the new volume.

[@vikash-tech-wizard]

I didn’t want to go that far, redoing networking and recreating all my containers. But yeah, completely reinstalling the container package when you have multiple volumes will present you the choice for a volume.

[@hotingot4067]

Thank you very much! a very clear explanation!

[@juebaitube]

Thank you Vikash ❤.

[@chrisipad4425]

it helps with my situation, thanks for your sharing!

[@monkeyvideo1029]

Thanks for the videos...very helpful! How did you create a virtual synology machine? That would be very helpful in testing different containers without risking my real data. TY

[@jaredplanz]

Thanks for this, Helpful with what I am looking to achieve.

[@vikash-tech-wizard]

You are welcome

[@rob28459]

But aren't the Docker image and container still located on volume1? IMHO only the configuration and mount are changed.

[@vikash-tech-wizard]

The image and container config is indeed still on volume1. These are used to create and start the container, the persistent data and config is what counts for performance. You can of course move the image to the new created volume but in my testing that is merely an administrative action.

[@iconfessimageekUK]

How do you move the Container manager package to volume 2?

[@vikash-tech-wizard]

I suppose delete the package, initialize a second volume. That way you can select a volume where to install packsges

[@kimsonvu]

@@vikash-tech-wizard I success do delete package and re-install it and move docker folder as your video.