-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Openshift failing to pull image #16971
Comments
@goldcakes |
Ok, thanks for the reply. Is there anyway to download my files without it or something. I need to submit my assignment before midnight. |
@tolusha is there any reason why it has to be pulled for every workspace start? Can't it be cached? Almost the whole day Che was unusable because of the quay.io issues... |
I see we have an issue with pull devfile registry image:
With nightly image the same. |
Fortunately, they managed to get it running in read-only mode. I would recommend you download your files now, as they are still working on the issue. This page shows regular updates about the issue. |
Ok, issue is currently resolved and stable. |
@danidoedel
corresponding issue #14698 |
Describe the bug
When I try starting Openshift.io it fails at pulling image "quay.io/eclipse/che-plugin-metadata-broker:v3.1.2"
Che version
Che version is 7.12.2 latest
Steps to reproduce
-Go to the openshift.io url
-Log in
-Go to workspaces
-Open a workspace
-Error is during start up
Expected behavior
Expected it to open the workspace in the php-simple start page
Screenshots
Installation method
Environment
Eclipse Che Logs
pulling image "quay.io/eclipse/che-plugin-metadata-broker:v3.1.2"
Error: ErrImagePull
Error: Failed to run the workspace: "Plugins installation process failed. Error: Unrecoverable event occurred: 'Failed', 'Error: ErrImagePull', 'workspacemlywc2fliee3ktsc.che-plugin-broker'"
Additional context
A friend of mine is also experiencing the same issue at their house.
I don't really know much about this, I'm using it to learn html at uni.
The text was updated successfully, but these errors were encountered: