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

The container images assume docker.io but don't explicitly reference docker.io #36

Open
seansund opened this issue Nov 11, 2022 · 0 comments
Labels
bug Something isn't working priority

Comments

@seansund
Copy link
Member

The container images are hosted on docker.io (not sure why they aren't available on quay!!!) but the base image registry is configured as turbonomic instead of docker.io/turbonomic. In many cases, the docker.io part is added automatically but we should be explicit and not rely on that.

On ARO clusters, OpenShift is configured to default to registry.redhat.io THEN docker.io for finding the default registry server. It just so happens that there is a version of the turbonomic images on registry.redhat.io that causes a failure

@seansund seansund added bug Something isn't working priority labels Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority
Projects
None yet
Development

No branches or pull requests

1 participant