Hi Guys

 

OK, I had an issue yesterday where my remote clients wouldnt connect to my nextcloud docker. I spotted there was an upgrade available, so I thought I'd upgrade it and try again... so I used the "Update" option from the docker screen and it ran really quickly and my nextcloud docker vanished completely from the list of dockers.

 

So, I thought first of all I would reboot the server and see if that resolved anything - but after a reboot it just says "Docker Service Failed to Start".

 

I took a snapshot of /mnt/user/system/docker/docker.img at this point - but not sure if this is too late?

 

I was thinking of deleting /mnt/user/system/docker/docker.img - restarting the docker service to see if it would start and create a new docker.img and then overwrite this new docker.img with the one I took a backup of?!?!

 

Before I make things worse I thought I'd ask if anyone can help?

 

Diagnostics attached.

dl380p-rack-diagnostics-20220504-0907.zip

Docker image looks fine, though it can easily be recreated if needed, first reboot and post new diags if it still doesn't start.

2 hours ago, JorgeB said:

Docker image looks fine, though it can easily be recreated if needed, first reboot and post new diags if it still doesn't start.

 

Those diags were this morning after rebooting at 5.30pm last night... I'll try another reboot at lunchtime and upload fresh diags - thanks

2 hours ago, JorgeB said:

Docker image looks fine, though it can easily be recreated if needed, first reboot and post new diags if it still doesn't start.

OK, just rebooted... same error message 😞

 

I have attached new diags.

dl380p-rack-diagnostics-20220504-1211.zip

It's the same:

 

May  4 12:09:27 DL380p-Rack emhttpd: shcmd (187): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 25
May  4 12:09:27 DL380p-Rack kernel: BTRFS: device fsid 030cf28d-7cc7-4e6b-9f35-00d4a0b332dd devid 1 transid 7231745 /dev/loop2 scanned by udevd (7588)
May  4 12:09:27 DL380p-Rack kernel: BTRFS info (device loop2): using free space tree
May  4 12:09:27 DL380p-Rack kernel: BTRFS info (device loop2): has skinny extents
May  4 12:09:27 DL380p-Rack root: Resize '/var/lib/docker' of 'max'
May  4 12:09:27 DL380p-Rack emhttpd: shcmd (189): /etc/rc.d/rc.docker start
May  4 12:09:27 DL380p-Rack root: starting dockerd ...
May  4 12:09:43 DL380p-Rack emhttpd: shcmd (191): umount /var/lib/docker
May  4 12:09:43 DL380p-Rack root: umount: /var/lib/docker: target is busy.
May  4 12:09:43 DL380p-Rack emhttpd: shcmd (191): exit status: 32

 

Docker image is mounting and I'm not seeing anything wrong with it, also don't see why it's failing to start the docker service, you can try re-creating the image, it might not help but it also won't hurt.

29 minutes ago, JorgeB said:

Docker image is mounting and I'm not seeing anything wrong with it, also don't see why it's failing to start the docker service, you can try re-creating the image, it might not help but it also won't hurt.

 

Thanks @JorgeB

 

Docker service has now started with no installed dockers... what is the easiest way to reinstall my dockers without losing their settings... rename the appropriate /mnt/user/appdata folder to something else, let the docker create a new appdata folder and then overwrite with the backup?

Just now, SliMat said:

reinstall my dockers without losing their settings.

Simply Apps, Previous Apps and check stuff off.  No renaming etc needs to be done.

Diagnostics showed your docker.img was completely full. After reinstalling your containers using Previous Apps, post new diagnostics. The usual reason for filling docker.img is an application writing to a path that isn't mapped to host storage.

Thanks @Squid that seems to have worked for the moment

 

Thanks @trurl the docker service is up and running now and attached are new diags - if you can spot anything awry I'd be grateful.

dl380p-rack-diagnostics-20220504-2348.zip

Did you reinstall your containers yet?

5 hours ago, trurl said:

Did you reinstall your containers yet?

 

Yes, they're all re-installed and running now. I didnt know there was a "previously installed" option from apps and this made the whole process so much easier than when I had to do a similar thing many years ago