Unmounting volume leaves the "backup volume"

[crazybrad]

@ joseph Thank you. I will try this process. @jdaviescoates Much appreciated tip about "dry run". I will combine your collective wisdom and go forth and conquer!

[crazybrad]

@joseph Completed the migration to the new server, but I ran into several errors restoring apps. Roughly 70% of the apps were in an error state, with a message similar to this one for Listmonk: Docker Error: Unable to pull image cloudron/app.listmonk.cloudronapp:202411131609490000. Please check the network or if the image needs authentication. statusCode: 500

The event log shows a successful attempt to restore again: App was restored from version 1.9.0 to version 1.9.0 using backup at 2024-12-14-150347-189/app_

but multiple attempts at this have failed. In all but two apps (Listmonk and Mail), retrying (with an occasional app restart) has gotten this to work for each app. Services have plenty of resources. The server is large. I am unable to try Recovery Mode for this app as the error state locks me out of that option (and the restarting option as well). (Rebooted the server. Mail restored next time, but ListMonk took ~ 2 more times to work)

Two One questions:

(1) How can I resolve this?

(2) - Why did this happen in the first place?

I followed the backup, restore, dry run, sync DNS, update certificates process and all seemed to work fine.

[joseph]

@crazybrad said in Unmounting volume leaves the "backup volume":

Listmonk: Docker Error: Unable to pull image cloudron/app.listmonk.cloudronapp:202411131609490000. Please check the network or if the image needs authentication. statusCode: 500

This is the ipv6 rate limit issue which many are hitting. dockerhub seems to pushed some bad implementation of rate limits and it's wholesale cutting off network providers from accessing dockerhub. We have a workaround in place now for the new release.