Named Volumes vs. Bind Mount


skipkayhil

Recommended Posts

I would recommend against it. The docker filesystem (where volumes are stored) on unRAID is kept in the loop mounted image you setup when setting up docker. The docker image is of limited size (resizing is a manual operation), limited in speed (due to the loop mounting), and you will often see the recommendation that if something goes wrong with docker to just delete the image a recreate all your containers (which also would delete volumes). Using bind mounts is the safer option and affords use the flexibility of using unRAIDs user share system to allow containers to store their data on the cache or array as we see fit. It also makes it easier to access the files (typically config files) that docker containers create as they are typically bind mounted to /mnt/user/appdata/container-name.  

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.