Restore after docker system prune --all --volumes --force

Isn't it as simple as running the docker-compose file again (if that's the way you run a container)?

docker-compose up -d

Zitat von liv

I've lost containers and volumes. Browsing on the backup repository I identified and copied back volumes and containers from mirrored /var/lib/docker, so files are back again. But I still cannot find them in Portainer GUI, so I'm still looking for a way to rescan objects from there.

Using "docker-compose up -d /var/lib/docker/containers/xxx" will relink them again to docker?

Using docker-compose up -d should link to the location where you stored your .yml files.

But how do you setup/run your containers , through Portainer or CLI or ...?

Zitat von liv

I used Portainer to setup and run them.

Then you can run them again from within Portainer.

Zitat von liv

The problem is that I have restored folders, but containers don't appear in the list on Portainer and I cannot start them.

Right now I'm looking for a way to update the list in Portainer to reflect the containers in the filesystem...

Aren't they visible in the Stacks tab in Portainer?

Zitat von liv

No Stacks tab contains an empty list.

Sorry, I can't help you with recovering a backup

The easiest way for me should be to setup the Stacks in Portainer from scratch (hope you have a backup from the settings) or setup everything with .yml files (those textfiles are easy to duplicate for a backup).

Maybe (and I hope) someone else can help you recovering you lost containers.

Zitat von liv

So I launched command "docker system prune --all --volumes --force",

Not trying to twist the knife but from where did you read to do this?

The only "prune" that (sometimes) need to be done is docker image prune to clear the leftovers of old images.

Volumes are binded to make sure they're persistent.

But, that you NOW know,

To try to solve your problem, since you have a backup:

Zitat von liv

I identified and copied back volumes and containers from mirrored /var/lib/docker, so files are back again

This is valid ONLY if you had your volumes under the docker root (/var/lib/docker).

Your approach is correct: copy all from "backup/var/lib/docker" to "/var/lib/docker" and your volumes/containers will be back in place.

Now the issue is:

Depending on how you edited the STACK before deploying, your volumes might be in a different path.

For e.g:

    volumes:
      - /srv/dev-disk-by-label-DATA/appdata/mosquitto/config:/mosquitto/config/

This volume is under /srv/dev-disk-by-label-DATA/appdata/mosquitto/config and NOT under /var/lib/docker/....

If deleted, even if I restore the docker root, ALL the configuration of the Container would be lost.

And when you ran that command, all volumes that were binded (and stopped), were deleted. (even if on a different path)

Prune unused Docker objects | Docker Documentation

If you have a copy of the YML (or the STACK) that you used to launch them in the beginning, that will might help to, at least, check if the DATA is still available.

Otherwise, you'll have to start blank.

I think you lost is the portaner volume which contains your stacks.

Now it depends, what the other containers were if you can recover.

1. First of all: go to the cli and stop the docker daemon systemctl stop docker
2. Next save the /var/lib/docker directory to some place and remember to keep the flafs / permissions
3. from you backup find the directory .../docker/volumes/portainer_data If you cant't find it you are out of luck if you find it continue
4. delete the directory /var/lib/docker/volumes/portainer_data (the original one, not the backup)
5. copy the directory back from your backup
6. restart the docker daemon systemctl start docker
7. check if the volume is found docker volume ls
8. report back here and we will see, if we can continue

I wonder why the docker volume disappeared, because think you had it running.

Soma ist not quite correct about the deletion of volumes.

In the example above

    volumes:
      - /srv/dev-disk-by-label-DATA/appdata/mosquitto/config:/mosquitto/config/

hhis is not volume in the docker terminology and will not be deleted by docker volume prune.

docker volume prune will only delete named volumes.

Zitat von Zoki

will not be deleted by docker volume prune.

docker volume prune will only delete named volumes.

You might be right,

Haven't read all docker documentation...............yet,

But, honestly, running a command with arguments "--all" and "--force" is a "invitation to disaster".

When I read it, I only remembered the "good-old-days" of friends of mine running "format c: /q" on a DOS window.