Uploaded image for project: 'Red Hat Service Interconnect (Skupper)'
  1. Red Hat Service Interconnect (Skupper)
  2. SKUPPER-1415

Skupper init fails with no understandable reason

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • 1.5.3
    • None
    • CLI, Container engine sites
    • None

      When running skupper init, if the user has not first logged on to registry.redhat.io, the init fails with an error that does not guide the user to log on with podman first.

      skupper init should provide guidance as to which registry it is trying to reach and whether podman has been logged on to the registry or not.

       

      $ skupper init --site-name MASTER --platform podman --ingress-host 10.10.10.15
      {{Error: Error initializing Skupper - error creating skupper component: skupper-router - error creating container skupper-router: [POST /libpod/containers/create][500] containerCreateLibpodInternalServerError  &

      {Because:image not known Message:[registry.redhat.io/service-interconnect/skupper-router-rhel9:2.4.3|http://registry.redhat.io/service-interconnect/skupper-router-rhel9:2.4.3]: image not known ResponseCode:500}

      }}

              fgiorget@redhat.com Fernando Giorgetti
              rhn-sa-brbaker Bryon Baker
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: