Issues with Docker going into read only mode


Recommended Posts

Why are you allocating 120G to docker.img? Have you had problems filling it? 20G is often more than enough, unless you have something misconfigured, and making it larger won't fix those problems, it will only make it take longer to fill. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Linux is case-sensitive, so any path configured within an application must match a container path, case-sensitive.

 

Also, why do you have your appdata, domains, system shares configured to be moved to the array? If these are on the array, dockers/VMs will have performance impacted by slower parity, and will keep array disks spunup since these files are always open.

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.