2025-03-29, 03:55 PM
(2025-03-29, 02:29 PM)FoodieFood Wrote: Thanks for the response! After checking, it seems the server version was outdated, and we now have 10.10.6 running on our setup with container manager/Synology. Updating the version however, completely wiped the old server (settings, users and indexed media), so we just reconfigured from scratch and are now waiting for the chance to test streaming again once the media hopefully syncs up.The issue is that you need to mount the /config folder to be outside the container.
Would you have any suggestions for maintaining smoother server updates like this in the future?
Thank you!
As the name implies, a container holds all relevant data for a service.
If you delete the container, you delete everything associated with it since all of that is inside of it.
Docker lets you host mount external directories outside of the container, and makes it accessible from the inside.
On a new install, you just need to set a host mount linked to /config on the inside.
Then when you build and start the container for the first time, it will populate all necessary things to wherever on your system you linked /config to.
Whenever you need to update containers, you simply link the place where your previous /config folder was mounted on.
Keep a mental note that updating Docker containers is not like updating regular programs.
You always need to make a new container and delete the old one. There's no way to update the image of an existing container, so you always have to start fresh for a new image version.
Host mounts lets you carry over content from past containers to newer ones as those remain after you delete a container.