-
Notifications
You must be signed in to change notification settings - Fork 17
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
Support for images NOT on docker hub? #5
Comments
Yeah, it would be helpful if that was configurable. We would like to use our Gitlab Dependency Proxy to cache images. |
I can probably make some changes for GHCR support at least, but out of curiosity, what are you guys using this script for? I mainly wrote this script for use cases where installing Docker wasn't feasible, but if it is, the real tools are going to be more robust. |
The "real" tools are mostly more bloated. :) We need it for vaultwarden, which recommends using docker-image-extract for when running docker isn't feasible. It's a ridiculous workflow and I'd prefer for vaultwarden to just provide binaries directly, but until that happens, docker-image-extract is faster and easier to implement than adding another containerization layer to our CI. |
I wanted to unpack Frigate, so I could build it into an LXC container. It used to be on docker hub (https://hub.docker.com/r/blakeblackshear/frigate) but then moved to https://ghcr.io/blakeblackshear/frigate:stable |
Trying to extract an image hosted somewhere other than docker hub, and getting:
I suspect this is our problem:
Would be great to be able to target an image somewhere other than docker hub.
The text was updated successfully, but these errors were encountered: