-
-
Notifications
You must be signed in to change notification settings - Fork 42
restore error #8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Solved this in my case by running |
Well, I already tried it. Will possibly work w. "default" images but not custom built. |
Ahh, got it. Misunderstood your setup. |
You're right we can improve this. Currently docker-backup only stores the image's name/tag and restores that information when restoring the backup. The image may have changed (or got deleted) in the meantime though, so we should additionally offering storing the image itself, too. |
I have an IDEA (not tested yet) |
"You're right we can improve this. Currently docker-backup only stores the image's name/tag and restores that information when restoring the backup. The image may have changed (or got deleted) in the meantime though" |
I made a small scripts in bash to backup the docker-compose and Dockerfile to build the image locally when I want to restore but the same thing happens to @andressepter Some idea?? Thanks for the time 8000 . |
+1 |
? |
I am getting 502 error when restoring from tar |
Tried to backup and restore alfresco instance. Backup runs well, but restore ends w. error:
Restoring Container with hostname: 25347149be76
Pulling Image: alfresco-content-services-cyber-alfresco:stable
Error response from daemon: pull access denied for alfresco-content-services-cyber-alfresco, repository does not exist or may require 'docker login'
Interetingly enough it restores alfresco database (postgres) and alfresco search services, all other containers get same error when restoring.
The text was updated successfully, but these errors were encountered: