-
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
Adding a container registry from Dashboard User preferences doesn't work #21589
Comments
The generated controller.devfile.io/devworkspace_pullsecret: 'true'
controller.devfile.io/watch-secret: 'true' but it only has EDIT: when adding the missing label then I am not able to start workspaces anymore, the workspace pod is terminated and recreated multiple times but never reach the running state. |
When I add
that's the devworkspace status:
and the events:
|
The DevWorkspace failing to start issue is caused by devfile/devworkspace-operator#897 and fixed by devfile/devworkspace-operator#898 |
Removing label |
Note that the fix lands in v0.15.3 upstream and will be in v0.16.0 downstream; there are no current plans to release v0.15.3 downstream (this can be changed if this issue is deemed important) |
@olexii4 could you please backport to 7.52.x and close? |
Closing this issue as the commit has been backported to 7.52.x now. |
sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-3316 |
Describe the bug
In Dashboard user preference it's possible to add a container registry:
But then:
Starting a workspace that use a private image fails:
The message on the dashboard doesn't provide the right information:
Running
podman pull
of private image fails:Che version
next (development version)
Steps to reproduce
podman pull
on private registryExpected behavior
If the user has provided added the container registry credentials in his profile:
podman pull <private image>
from within a workspace should workIf the user has NOT added the container registryin his profile:
authorization failure
we should report it in the error message and suggest the user to add the container registry credentials in his user profileRuntime
OpenShift
Installation method
OperatorHub
Environment
Dogfooding instance
Release Notes Text
If a user added a container registry credential in Eclipse Che User Dashboard, that credential was not used to pull images from the registry resulting in workspaces failing to start.
The text was updated successfully, but these errors were encountered: