Jump to content

Unwanted disk mounting & docker file storage behavior


Recommended Posts

Posted

When did the ability to create my own directory under /mnt (/mnt/docker-appdata/data) become a forbidden mount point for the docker data area?  I needed to shut down my dockers so that I could replace the drive the data is stored on (usually mounted under /mnt/docker-appdata/ with the data directory located in the root of that particular drive).  When I tried to turn dockers back on, that directory ends up turning red, and then the system says that I need to enter it in the format required.  This has always worked in the past, been set up that way on my system since dockers were enabled.  I don't WANT to mount that under /mnt/disks (another issue I have a problem with) and map from there, and I definitely don't want my docker information on the array.

 

I also have a problem with Unassigned Devices not allowing me to mount new drives wherever I want under /mnt (it forces me to use /mnt/disks), although I had it mounting several drives under the main /mnt directory (and still have 2 that do, unless I try to modify them then my mount points are screwed up).

 

Is this 'feature' of not allowing me to put stuff where I want able to be disabled, or am I going to have to reconfigure my entire setup because someone else decided they knew better where my stuff should be mounted?

 

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.

×
×
  • Create New...