-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
quay.io - Provide alternative for docker images #157
Comments
You can use
for the time of failure :-) |
I just tried to download images on new machine and it can’t download the
images
…On Thu, 28 May 2020 at 16:17, Lukasz Bajsarowicz ***@***.***> wrote:
You can use
warden env pull --ignore-pull-failures || true
for the time of failure :-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOJOUM3NPAO6INYFTYRY3TRTZP7HANCNFSM4NNCPSTA>
.
|
Same exact errors here (screenshot). Big ouch Quay When I moved the images to Quay back in January it was largely for 2 reasons: a) Needed to split images into repository per image for better tag structure (they already had to be renamed beyond just the prefix) Since that time I've discovered there is no way to have a transparent image caching server in front of Quay — as I do with Docker Hub to avoid downloading images multiple times to individual workstations and VMs — and they've had a major outage at least three times. Apparently the assumption that Quay as a long-standing image registry now owned by RedHat would mean it stayed online and was stable was misplaced. They were down for almost the entire day on the 19th and have been down for nearly an hr now. 🤦 Thanks for the heads up @ihor-sviziev; might not have noticed it myself this morning. Think the verdict is clear, the images need to be moved back to Docker Hub, the question that remains is where and what the names should be. These are the current images loading from Quay.io:
The org name
...OR select an alternate name for use as an Org on Docker Hub to push them into. I'd go with Thoughts? |
Quick update here: All docker images have been re-located to a new Docker Hub organization and Warden 0.5.1 released with updated environment configuration referencing these images. See the release notes for further details: https://docs.warden.dev/changelog.html#version-0-5-1-2020-05-28 |
Right now quay.io has an outage, as result we can't download docker images
![image](https://user-images.githubusercontent.com/1873745/83146122-7eefbf00-a0fe-11ea-93b4-f77f3d544a91.png)
Maybe it's better to add all images to docker hub?
The text was updated successfully, but these errors were encountered: