8000 restore error · Issue #8 · muesli/docker-backup · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

Open
andressepter opened this issue Nov 24, 2020 · 10 comments
Open

restore error #8

andressepter opened this issue Nov 24, 2020 · 10 comments
Labels
enhancement New feature or request

Comments

@andressepter
Copy link

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.

@walkention
Copy link

Solved this in my case by running docker pull <image-name> before running the restore. Still an issue though.

@andressepter
Copy link
Author

Well, I already tried it. Will possibly work w. "default" images but not custom built.
Also tried to generate local repository w. custom built alfresco images (work in progress currently).

@walkention
Copy link

Ahh, got it. Misunderstood your setup.

@muesli
Copy link
Owner
muesli commented Nov 25, 2020

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.

@muesli muesli added the enhancement New feature or request label Nov 25, 2020
@andressepter
Copy link
Author

I have an IDEA (not tested yet)
During backup I will create my very own local repository. During restore I will add "localhost:5000" (or what ever location I coose) to the json file. Have to try it out.
And yes - ability to backup WHOLE docker container (whatever its origin may be, a standard or self-built) and restore it with data volumes will absolutely ROCK!
There is no such script / program out there. I have been struggiling w. full container backup / restore 2 weeks now (Ive also re-created (ugly and clumsy) replica of your code in BASH) w. no good results.

@andressepter
Copy link
Author

"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"
One addition : I already tried this scenario 1. build alfresco codebase from scratch 2. restore images OVER working codebase. -- still it tries to download images from docker.io although image lies right there locally.

@GoldraK
Copy link
GoldraK commented Aug 24, 2021

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 .

@andreasotto
Copy link

+1

@andreasotto
Copy link
Restoring Container: traefik_reverse-proxy_1
Pulling Image: traefik:v2.4
Error response from daemon: No such image: traefik:v2.4

?

@mauamolat
Copy link

I am getting 502 error when restoring from tar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants
0