Docker unable to start


Recommended Posts

Your docker image is corrupt. Have you had problems filling it? You will have to delete it in Settings - Docker and recreate it. Then you can reinstall your dockers just as they were using the Previous Apps feature on the Apps page.

 

Possibly you have some issues with the way one or more of your dockers is setup though which has caused these issues. What docker do you run?

Link to comment

Name                              Container     Writable          Log
---------------------------------------------------------------------
binhex-minecraftbedrockserver       3.46 GB      1.43 GB      4.66 kB
binhex-minecraftbedrockserver2      3.46 GB      1.43 GB      4.44 kB
binhex-krusader                     2.47 GB      16.4 MB      16.7 kB
freepbx                                2 GB          0 B      22.8 MB
binhex-nzbhydra2                    1.11 GB      74.9 MB      71.9 kB
plex                                 724 MB       302 MB      6.67 kB
sonarr                               622 MB      21.1 MB      24.2 kB
ombi                                 606 MB       230 MB      11.4 kB
radarr                               574 MB      22.4 MB      16.1 kB
NginxProxyManager                    529 MB       193 kB      60.1 kB
HandBrake                            504 MB      85.3 kB      19.4 kB
nextcloud                            354 MB      40.2 kB      4.89 kB
Nextcloud-DB                         351 MB       344 kB      4.43 kB
NginxProxyManager-DB                 351 MB       344 kB      4.43 kB
sabnzbd                              260 MB       303 kB      9.55 kB
headphones                           232 MB      18.2 MB      9.18 kB
steamwise                            204 MB          0 B      7.48 kB
steamwise2                           204 MB          0 B      6.43 kB
m3u8                                 167 MB      39.6 kB      7.41 kB
transmission                        78.1 MB      9.58 kB      6.92 kB
 

 

I did a bit of clean up of some containers that were kicking around.  This is what remains.

Link to comment
16 minutes ago, johnnie.black said:

Cache fs is OK but it's full, docker image ran out of space, and that's causing the problems.

Is this why your cache is so full?

5 minutes ago, trurl said:

You have cache-no shares anonymized as d----------p and T-------e with files on cache and they will not be moved.

 

Link to comment
1 minute ago, trurl said:

Is this why your cache is so full?

 

I had two empty folders on cache that shouldnt have been there based on the cache-no shares.  No content in them but they have been removed now.

 

My cache disk is fairly full because I have 3 VMs with relatively large disks running on cache.  That plus the Docker sizes consume most space.

Link to comment
22 minutes ago, trurl said:

You have cache-no shares anonymized as d----------p and T-------e with files on cache and they will not be moved.

What are these shares anonymized as d----------p and T-------e ?

 

As I explained, mover ignores cache-no shares. If a share already has files on cache, setting the share to cache-no will not get any of those files off cache. The user share settings only applies to newly written files. So if a share has files on cache, and you set it to cache-no, no more files for that share will be written to cache, but mover will ignore the share and so those files will never be moved from cache.

Link to comment
13 hours ago, trurl said:

What are these shares anonymized as d----------p and T-------e ?

 

As I explained, mover ignores cache-no shares. If a share already has files on cache, setting the share to cache-no will not get any of those files off cache. The user share settings only applies to newly written files. So if a share has files on cache, and you set it to cache-no, no more files for that share will be written to cache, but mover will ignore the share and so those files will never be moved from cache.

Those were two empty folders.  When I changed the shares to no longer be on the cache drive some time ago, I had moved them off to the array but forgot the root share folder (which was empty).  All the content inside were moved off to array already.  Those empty folders have been removed from the cache

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.