skupper.v2.system fails to pull router image from authenticated registry #72
Description
When using the 2.0 collection, pointing to the released 2.0.1 cli image, my playbooks fail:
TASK [skupper.v2.system] *********************************************************************************
task path: /skupper-test-kitchen-sink/setup.yaml:58
fatal: [system-backend-1]: FAILED! => changed=false
msg: |-
error setting up 'system-backend-1' namespace: Sources will be consumed from namespace "system-backend-1"
Failed to bootstrap: failed to render site state: failed to pull router image SOME_REGISTRY/service-interconnect/skupper-router-rhel9:3.3.1: error pulling image SOME_REGISTRY/service-interconnect/skupper-router-rhel9:3.3.1: unexpected error
Recommendation:
If the image is being pulled from an authenticated registry,
make sure to log in first, using:
docker login <registry-url>
In case you are using a custom authentication file, you should
set the REGISTRY_AUTH_FILE environment variable.
My guess is that the CLI, being run from a container, does not have access to the registry login data for the user. I know the login is otherwise working, as the CLI image itself came from there.
I believe this may be the same for the 2.1 collection; I didn't see it yet just because I'm pointing to a different registry for that, which requires no authentication.
Metadata
Metadata
Assignees
Labels
No labels