Restore only restores volumes

[addohm]

Theres probably more that I'm expected to know but as far as I can tell this script backs everything up to a text file in JSON format, and the volume, but when I restore, it only restores the volume. How do I restore the rest?

[piscue]

true that. I think it should be quite easy to add on the restore process

[gingerbeardman]

a full restore script seems essential, if only to test that the backup is working?

[kaineuk]

did u have any luck with the restore ic got the same prob it only restories volume and most of my containers work from the /portainer/Files/AppData/Config folder and i dont no how to restore this way lol

[piscue]

Fixed in PR #19.

The restore script was only sourcing restore-volumes.sh. Three things were missing and are now added:

restore/restore-images.sh — runs docker load -i for each saved image tar, so images come back without needing to pull from a registry.

restore/restore-containers.sh — reads the saved docker inspect JSON and reconstructs the docker run command (name, image, env, ports, named volumes, bind mounts, restart policy, network mode). Containers are recreated in the correct state; use -f to replace any that already exist.

restore/restore-bind-mounts.sh — for containers like Portainer that store config under host paths (e.g. /portainer/Files/AppData): pass -B when backing up and restoring to include those host directories. A manifest.json per container maps each archive back to its original path.

Restore order is now: images → volumes → bind-mount host paths → containers.

A full end-to-end integration test (Docker-in-Docker) verifies the complete cycle: backup, wipe everything including the image, restore, and assert the container is running with its volume data, bind-mount files, env vars, restart policy, and port mappings all intact.