Jump to content

Disaster - Dockers Corrupted? Destroyed?


Profezor

Recommended Posts

Disaster - Dockers Corrupted? Destroyed?

Help

1.Error At the bottom of my Docker list in the Docker tab.

/usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.phpon line 90

2. Within Share - AppData says to many files to list

3. Within Finder - AppDat Folder appears empty

4. Backup folder is (appears) empty

5. Usually in Settings - Docker - You get the option to delete the image, which was done, but that option is no longer there.

6. When I try to add containers, no files are pull and I get errors. Typically a Server Error and it is not recreated.

 

Only good thing is that I have all my files within share.

 

Running version 6.9.2

Here is a screenshot Docker Service

 

Any ideas? 

Screenshot 2021-09-01 at 08.21.29.png

Edited by Profezor
Link to comment

I lost my appdata. Some how the contents of my appdata is either gone or invisible.

All my shares are still there and assessable.

 

My docker tab produces this error

Warning: file_put_contents(/var/lib/docker/unraid/images/unmanic-icon.png): failed to open stream: Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.phpon line 90

 

My question - How do I fix this? Can I reinstall all my dockers to make my system usable again? I hate to 

configure all my dockers again, but at this point I just need them back

 

My docker templates are there but won't reinstall.

 

I just downgraded to 6.9.1 to see if that would fix this docker error but no luck.

Link to comment
19 minutes ago, JonathanM said:

File(s) plural? It should only be one zip file.

That is the error when I try to upload THE SINGLE ZIP FILE.

 

Sorry, but my system has been unusable for over a week. I really need to get my dockers back and working and I am not getting anywhere. 😞

Edited by Profezor
Link to comment

Unrelated, but connection problems with parity. You should shutdown and check connections, power and SATA, including splitters.

 

Corrupt docker.img. Why have you given it 150G? Have you had problems filling it? 20G is often more than enough. Making it larger won't fix filling it, it will only make it take longer to fill. The usual cause of filling docker.img is an app writing to a path that isn't mapped.

 

Why are you moving appdata, domains, system shares to the array? You want these shares to be cache-prefer so they will stay on cache. If they are on the array, dockers/VMs will not perform as well, and they will keep array disks spinning because these files are always open.

 

Set these shares to cache-prefer.

 

Disable VM Manager in Settings. Disable Docker in Settings and delete docker.img.

 

While you have Dockers/VMs disabled, run mover so those shares will get moved to cache where they belong.

 

After mover finishes, recreate docker.img, try 20G.

 

https://wiki.unraid.net/Manual/Troubleshooting#How_do_I_recreate_docker.img.3F

 

Reinstall your dockers

https://wiki.unraid.net/Manual/Troubleshooting#Restoring_your_Docker_Applications

 

You should run a non-correcting parity check just to confirm your parity connections are fixed.

 

Post new diagnostics if you have any problems or need further advice.

Link to comment
On 9/15/2021 at 1:07 AM, trurl said:

Unrelated, but connection problems with parity. You should shutdown and check connections, power and SATA, including splitters.

 

Corrupt docker.img. Why have you given it 150G? Have you had problems filling it? 20G is often more than enough. Making it larger won't fix filling it, it will only make it take longer to fill. The usual cause of filling docker.img is an app writing to a path that isn't mapped.

 

Why are you moving appdata, domains, system shares to the array? You want these shares to be cache-prefer so they will stay on cache. If they are on the array, dockers/VMs will not perform as well, and they will keep array disks spinning because these files are always open.

 

Set these shares to cache-prefer.

 

Disable VM Manager in Settings. Disable Docker in Settings and delete docker.img.

 

While you have Dockers/VMs disabled, run mover so those shares will get moved to cache where they belong.

 

After mover finishes, recreate docker.img, try 20G.

 

https://wiki.unraid.net/Manual/Troubleshooting#How_do_I_recreate_docker.img.3F

 

Reinstall your dockers

https://wiki.unraid.net/Manual/Troubleshooting#Restoring_your_Docker_Applications

 

You should run a non-correcting parity check just to confirm your parity connections are fixed.

 

Post new diagnostics if you have any problems or need further advice.

Midway report.

 

I have recreated docker.img

i can now see my  appdata folders in the share tab. Progress 
 

but docker service will not start. I get the following error..

 

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 682
Couldn't create socket: [2] No such file or directory
Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 866

 

Running a parity check with correction but is scheduled to run for 200 days at this rate.

I can stop and repost thee latest diagnostics or ?

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.

×
×
  • Create New...