search

EideardVMR / unraid-easybackup

Snapshot for virtual machines and backups for them, as well as for Docker
GNU General Public License v3.0
7 stars 1 forks source link

lost all containers #11

Open 7eptem opened 6 months ago

7eptem commented 6 months ago

just started do to my first backup and when the plugin finished i lost all my containers

EideardVMR commented 6 months ago

Hi, it is almost impossible that this has occurred due to the backup. The procedure is that the container is shut down (via the Unraid Docker integration) and then a backup is created in the corresponding binds, which are read-only. The Docker is then started up again (via the Unraid Docker integration). So the entire write process in the Docker itself runs via the Docker API.

The only thing you could have caused problems with is that your target path for the Docker is in appdata. But even with that, you wouldn't lose all containers.

Have only the containers disappeared or also the binds (i.e. the folders in appdata)?

7eptem commented 6 months ago

Hi, it is almost impossible that this has occurred due to the backup. The procedure is that the container is shut down (via the Unraid Docker integration) and then a backup is created in the corresponding binds, which are read-only. The Docker is then started up again (via the Unraid Docker integration). So the entire write process in the Docker itself runs via the Docker API.

The only thing you could have caused problems with is that your target path for the Docker is in appdata. But even with that, you wouldn't lose all containers.

Have only the containers disappeared or also the binds (i.e. the folders in appdata)?

just the containers, but i think that was a visual bug, because docker will not start , folders are intact as far i can see the single thing i see now is that he broke my plex container, is not working anymore, for some reason he deleted the preferances.xml file in plex

EideardVMR commented 6 months ago

OK, if Docker itself does not start or is not started, the problem is somewhere in the Docker system of Unraid.

Because I only use the Docker socket here in which I execute 3 commands: start, stop, status information

There are no write operations on the appdata, so nothing can break here.

With the VMs it looks a little different, here snapshot files are created and temporary json files.

If the container is affected, you can also re-import the template, as Unraid always stores this. You can then find it under "Add Container" image