Skip to content
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

Automatic 'podman login' with configured container registry not working #22987

Closed
AObuchow opened this issue May 28, 2024 · 3 comments
Closed
Assignees
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.

Comments

@AObuchow
Copy link

Describe the bug

After having configured a container registry in User Dashboard, new workspaces are not being automatically logged into the configured container registries. I tried with quay.io and docker.io and neither worked.

This is currently reproducible in the 3.14 builds of DevSpaces and on the dogfooding cluster.

Che version

7.86@latest

Steps to reproduce

  1. Configure a container registry from the User Dashboard's User Preferences (click on the gravatar in the top right of the dashboard -> user preferences -> add a container registry with your credentials.
  2. Start a workspace
  3. Open a terminal and run podman login --get-login <container-registry>. For example: podman login --get-login quay.io
  4. You'll see Error: not logged into <container-registry>. E.g. Error: not logged into quay.io

Expected behavior

We should already be logged into the configured container registries.
For example, if quay.io is configured as a container registry, the output of podman login --get-login quay.io should be your quay.io username.

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response

@AObuchow AObuchow added kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. area/dashboard labels May 28, 2024
@AObuchow
Copy link
Author

I can see that the associated kubernetes.io/dockercfg, kubernetes.io/dockerconfigjson are being created, and the dockerconfigjson has the appropriate value. Perhaps some other error is occurring when running the podman login command that's being "swallowed" by the || true.

@tolusha
Copy link
Contributor

tolusha commented May 29, 2024

Hello, @AObuchow
I've tried on dogfooding cluster (+minikube cluster), but I wasn't able to reproduce the issue unfortunately.

@AObuchow
Copy link
Author

@tolusha After looking into this further, I believe the podman login command needs to surround the username and password with single quotes '' to support any "special characters" such as !, so that they aren't interpreted by bash.

aobuchow@fedora:~$ echo !test
bash: !test: event not found
aobuchow@fedora:~$ echo '!test'
!test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

2 participants