Update to v2.6.0 error ImagePullBackOff

MelvinBMelvinB
Community Member

Hello all.

Currently running the SCIM bridge in Azure Kubernetes and trying to update to v2.6.0 using the command: kubectl set image deploy/op-scim-bridge op-scim-bridge=1password/scim:v2.6.0

However, unfortunately I am getting the errors ImagePullBackOff and ErrImagePull on the pod. See below the logs. Anything I can do to fix this? Thanks!

Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 39s default-scheduler Successfully assigned default/op-scim-bridge-d6f5c469d-xvfxr to aks-agentpool-38680737-vmss000001
Warning Failed 39s kubelet Failed to pull image "1password/scim:v2.6.0": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/1password/scim:v2.6.0": failed to resolve reference "docker.io/1password/scim:v2.6.0": failed to do request: Head "https://registry-1.docker.io/v2/1password/scim/manifests/v2.6.0": dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:58517->[::1]:53: read: connection refused
Warning Failed 23s kubelet Failed to pull image "1password/scim:v2.6.0": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/1password/scim:v2.6.0": failed to resolve reference "docker.io/1password/scim:v2.6.0": failed to do request: Head "https://registry-1.docker.io/v2/1password/scim/manifests/v2.6.0": dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:47805->[::1]:53: read: connection refused
Normal BackOff 11s (x2 over 39s) kubelet Back-off pulling image "1password/scim:v2.6.0"
Warning Failed 11s (x2 over 39s) kubelet Error: ImagePullBackOff
Normal Pulling 0s (x3 over 39s) kubelet Pulling image "1password/scim:v2.6.0"
Warning Failed 0s (x3 over 39s) kubelet Error: ErrImagePull
Warning Failed 0s kubelet Failed to pull image "1password/scim:v2.6.0": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/1password/scim:v2.6.0": failed to resolve reference "docker.io/1password/scim:v2.6.0": failed to do request: Head "https://registry-1.docker.io/v2/1password/scim/manifests/v2.6.0": dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:55225->[::1]:53: read: connection refused


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided

Comments

  • laz.h_1Plaz.h_1P

    Team Member

    Hi Melvin! I'm sorry to hear that you are experiencing this issue when trying to update your SCIM bridge. From taking a look at your logs, it seems that your pod is having trouble resolving the DNS record of the docker registry. Have you tried upgrading by bumping your docker-compose.yml file instead of running a command in the pod? More instructions can be found here. If that doesn't work, its possible that the server your cluster is running on has a problem with its DNS configuration. Is this your first time upgrading the SCIM bridge, or has it worked previously and is now giving you trouble?

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file