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

Image for repository does not exist #292

Closed
psschwei opened this issue Mar 16, 2023 · 8 comments
Closed

Image for repository does not exist #292

psschwei opened this issue Mar 16, 2023 · 8 comments
Assignees
Labels
bug Something isn't working priority: low Low priority

Comments

@psschwei
Copy link
Collaborator

Steps to reproduce the problem

Deploy on kubernetes via helm

What is the current behavior?

$ k get po -n ray quantum-serverless-repository-796588bfcb-8xprv -o json | jq '.spec.containers[].image'
"qiskit/quantum-repository-server:latest"

$ k get po -n ray quantum-serverless-repository-796588bfcb-8xprv
NAME READY STATUS RESTARTS AGE
quantum-serverless-repository-796588bfcb-8xprv 0/1 ImagePullBackOff 0 3m50s

$ k get events -n ray | grep repository
6m1s Normal Scheduled pod/quantum-serverless-repository-796588bfcb-8xprv Successfully assigned ray/quantum-serverless-repository-796588bfcb-8xprv to kind-control-plane
57s Warning DNSConfigForming pod/quantum-serverless-repository-796588bfcb-8xprv Search Line limits were exceeded, some search paths have been omitted, the applied search line is: ray.svc.cluster.local svc.cluster.local cluster.local ibmuc.com ibmmodules.com s81c.com
4m3s Normal Pulling pod/quantum-serverless-repository-796588bfcb-8xprv Pulling image "qiskit/quantum-repository-server:latest"
3m37s Warning Failed pod/quantum-serverless-repository-796588bfcb-8xprv Failed to pull image "qiskit/quantum-repository-server:latest": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/qiskit/quantum-repository-server:latest": failed to resolve reference "docker.io/qiskit/quantum-repository-server:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
3m37s Warning Failed pod/quantum-serverless-repository-796588bfcb-8xprv Error: ErrImagePull
3m13s Normal BackOff pod/quantum-serverless-repository-796588bfcb-8xprv Back-off pulling image "qiskit/quantum-repository-server:latest"
3m13s Warning Failed pod/quantum-serverless-repository-796588bfcb-8xprv Error: ImagePullBackOff
6m1s Normal SuccessfulCreate replicaset/quantum-serverless-repository-796588bfcb Created pod: quantum-serverless-repository-796588bfcb-8xprv
6m1s Normal ScalingReplicaSet deployment/quantum-serverless-repository Scaled up replica set quantum-serverless-repository-796588bfcb to 1

Also, https://hub.docker.com/r/qiskit/quantum-serverless-repository returns a 404

What is the expected behavior?

Image deploys normally

@psschwei psschwei added the bug Something isn't working label Mar 16, 2023
@akihikokuroda akihikokuroda self-assigned this Mar 16, 2023
@akihikokuroda
Copy link
Collaborator

If I understand the actions correctly, the push to the docker hub happens when the release is cut or every night. The action hasn't executed since the repository-project was merged into the main. It should be pushed tonight.

@psschwei
Copy link
Collaborator Author

ah, good point (didn't realize that just merged today)

@Tansito
Copy link
Member

Tansito commented Mar 17, 2023

oh, this is good point out @akihikokuroda , thank you

@Tansito Tansito added the priority: low Low priority label Mar 17, 2023
@psschwei
Copy link
Collaborator Author

Somewhat related (though this might be more for the Qiskit team) is whether the recent Docker announcement impacts the repo for our images...

@akihikokuroda
Copy link
Collaborator

@psschwei
Copy link
Collaborator Author

As of now, the pod still fails on install with an ImagePullBackoff status, because the only image in the repo is the nightly tag, and the chart is looking for the latest tag.

Is it possible to either (a) tag the nightly build with the latest tag for the time being, or (b) cut a new dot release, which I assume would include a latest tag for the repository image?

@psschwei psschwei reopened this Mar 20, 2023
@IceKhan13
Copy link
Member

Good point. We will cut release tomorrow with repository and possibly gateway

@akihikokuroda
Copy link
Collaborator

#328 fix this.

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: low Low priority
Projects
None yet
Development

No branches or pull requests

4 participants