Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-6555

Automatic 'podman login' with configured container registry not working

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Hide
      = Automatic Podman login with configured container registry not working

      Previously, after configuring container registries (quay.io, docker.io, etc.) from the User Dashboard and starting a workspace, you were not automatically logged into the configured registries. The defect has been fixed in this release.
      Show
      = Automatic Podman login with configured container registry not working Previously, after configuring container registries (quay.io, docker.io, etc.) from the User Dashboard and starting a workspace, you were not automatically logged into the configured registries. The defect has been fixed in this release.
    • Bug Fix
    • Done
    • Workaround Exists
    • Hide

      Log into the container registry from workspace terminal using podman login command with credentials

      Show
      Log into the container registry from workspace terminal using podman login command with credentials

      Description of problem:

      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.

       

      Upstream Che Issue: https://github.com/eclipse-che/che/issues/22987

       

      Prerequisites (if any, like setup, operators/versions):

      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

       

      Actual results:

      'Error: not logged into quay.io' }} {{when running 'podman login --get-login <container-registry>'

      Expected results:

      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.

      Reproducibility (Always/Intermittent/Only Once):

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

       

       *

              abazko Anatolii Bazko
              aobuchow Andrew Obuchowicz
              Serhii Skoryk Serhii Skoryk
              Jana Vrbkova Jana Vrbkova
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: