Closed formeo14 closed 2 months ago
And what is the best way to restore my deleted containers?
Fixed in v0.16.0-unstable59 thanks for reporting to restore your container, check the backup in the cosmos-backup zip in the config folder
Thank you! That was fast!
It appears that there is only one backup in the cosmos-backup.zip file. Consequently, there seems to be no way to restore the containers from the backup because it was noticed too late. The backup appears to be overwritten by a new one.
If you haven't got any backup software on that folder to produce a history of the file version (ex. Restic) then I am afraid you might not be able to recover an older version, sorry I will definitely add backup as a feature in Cosmos, but until then you have to use an external software to manage any sort of backup of your setup
What happened?
Hello,
I've been using the unstable branch for a while now, but I've noticed that the new branch is deleting containers that are running in a network through Gluetun. It attempts to update them but then says the hostname doesn't match, so it removes the container. This didn't happen in version 0.15.7, where the containers could update normally. It happens to a lot of my Servapps now!
What should have happened?
The update should proceed normally or restore the previous container configuration, as it was able to run smoothly despite encountering the "Error response from daemon: conflicting options: hostname and the network mode." It's quite a hassle to set up Gluetun on Cosmos, but it is possible. Now, Cosmos is deleting all containers that are updating and running through Gluetun, which should not occur. This disruption completely undermines the entire setup.
How to reproduce the bug?
Relevant log output
Other details
No response
System details