Can't pull registry.hub.docker.com/library/mongo:4.2.6

[Aonauma]

What did you do to encounter the bug?
Steps to reproduce the behavior:

1. Deploy and Configure a MongoDB Resource follow documents
2. Replace in config/samples/mongodb.com_v1_mongodbcommunity_cr.yaml to the password
3. Invoke the following kubectl command

kubectl apply -f config/samples/mongodb.com_v1_mongodbcommunity_cr.yaml --namespace <my-namespace>

I found the error can't pull registry.hub.docker.com/library/mongo:4.2.6
Could you please help me to this solution well soon?

[bznein]

Hi @Aonauma,

I was able to reproduce the issue, and it looks like for some reason dockerhub has changed how to pul images.

before, it was possible to do docker pull registry.hub.docker.com/library/mongo:4.2.6but not it can only be either docker pull mongo:4.2.6 or docker pull library/mongo:4.2.6

While we try to understand if this is a permanent change, you can try one of the two following solutions:

1. Pull the image locally (with one of the two commands mentioned above), then push it to another registry (e.g. quay) and change the MONGODB_IMAGE and MONGODB_URL values here https://github.com/mongodb/mongodb-kubernetes-operator/blob/master/config/manager/manager.yaml#L35 to point to the new repo
2. CHange MONGODB_IMAGE to be only mongo and MONGODB_URL to be library. I just tried this workaround and I was able to pull the image.

Let me know if this helps!

[Aonauma]

Dear all, I will tried this solution two. I still found the error same before cannot pull image

…

On Tue, 22 Jun 2564 BE at 15:26 Nikolas De Giorgis ***@***.***> wrote: Hi @Aonauma <https://github.com/Aonauma>, I was able to reproduce the issue, and it looks like for some reason dockerhub has changed how to pul images. before, it was possible to do docker pull registry.hub.docker.com/library/mongo:4.2.6but not it can only be either docker pull mongo:4.2.6 or docker pull library/mongo:4.2.6 While we try to understand if this is a permanent change, you can try one of the two following solutions: 1. Pull the image locally (with one of the two commands mentioned above), then push it to another registry (e.g. quay) and change the MONGODB_IMAGE and MONGODB_URL values here https://github.com/mongodb/mongodb-kubernetes-operator/blob/master/config/manager/manager.yaml#L35 to point to the new repo 2. CHange MONGODB_IMAGE to be only mongo and MONGODB_URL to be library. I just tried this workaround and I was able to pull the image. Let me know if this helps! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#585 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGXLXVTAWHDYCC5FDOJOFEDTUBCLBANCNFSM47DCETPA> .

[bznein]

@Aonauma can you please show me the output of

kubectl describe deployment mongodb-kubernetes-operator

and

kubectl describe statefulset example-mongodb

Please note that you will have to delete the pod that is failing to pull the image so that it gets rescheduled with the new image field and it should be able to pull from the right one

[Aonauma]

Dear All, Output $ kubectl describe deployment/mongodb-kubernetes-operator -n poc-mongodb Name: mongodb-kubernetes-operator Namespace: poc-mongodb CreationTimestamp: Tue, 22 Jun 2021 16:13:10 +0700 Labels: app.kubernetes.io/managed-by=Helm Annotations: deployment.kubernetes.io/revision: 1 meta.helm.sh/release-name: poc-mongodb-operator meta.helm.sh/release-namespace: poc-mongodb Selector: name=mongodb-kubernetes-operator Replicas: 1 desired | 1 updated | 1 total | 1 available | 0 unavailable StrategyType: RollingUpdate MinReadySeconds: 0 RollingUpdateStrategy: 25% max unavailable, 25% max surge Pod Template: Labels: name=mongodb-kubernetes-operator Service Account: mongodb-kubernetes-operator Containers: mongodb-kubernetes-operator: Image: quay.io/mongodb/mongodb-kubernetes-operator:0.6.1 Port: <none> Host Port: <none> Command: /usr/local/bin/entrypoint Environment: WATCH_NAMESPACE: (v1:metadata.namespace) POD_NAME: (v1:metadata.name) OPERATOR_NAME: mongodb-kubernetes-operator AGENT_IMAGE: quay.io/mongodb/mongodb-agent:10.29.0.6830-1 VERSION_UPGRADE_HOOK_IMAGE: quay.io/mongodb/mongodb-kubernetes-operator-version-upgrade-post-start-hook:1.0.2 READINESS_PROBE_IMAGE: quay.io/mongodb/mongodb-kubernetes-readinessprobe:1.0.4 MONGODB_IMAGE: mongo MONGODB_REPO_URL: registry.hub.docker.com Mounts: <none> Volumes: <none> Conditions: Type Status Reason ---- ------ ------ Available True MinimumReplicasAvailable Progressing True NewReplicaSetAvailable OldReplicaSets: <none> NewReplicaSet: mongodb-kubernetes-operator-6567c6b547 (1/1 replicas created) Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal ScalingReplicaSet 3m19s deployment-controller Scaled up replica set mongodb-kubernetes-operator-6567c6b547 to 1 And then $ kubectl describe statefulset/example-mongodb -n poc-mongodb Name: example-mongodb Namespace: poc-mongodb CreationTimestamp: Tue, 22 Jun 2021 16:13:17 +0700 Selector: app=example-mongodb-svc Labels: app=example-mongodb-svc Annotations: <none> Replicas: 3 desired | 1 total Update Strategy: RollingUpdate Pods Status: 0 Running / 1 Waiting / 0 Succeeded / 0 Failed Pod Template: Labels: app=example-mongodb-svc Service Account: mongodb-kubernetes-operator Init Containers: mongod-posthook: Image: quay.io/mongodb/mongodb-kubernetes-operator-version-upgrade-post-start-hook:1.0.2 Port: <none> Host Port: <none> Command: cp version-upgrade-hook /hooks/version-upgrade Environment: <none> Mounts: /hooks from hooks (rw) mongodb-agent-readinessprobe: Image: quay.io/mongodb/mongodb-kubernetes-readinessprobe:1.0.4 Port: <none> Host Port: <none> Command: cp /probes/readinessprobe /opt/scripts/readinessprobe Environment: <none> Mounts: /opt/scripts from agent-scripts (rw) Containers: mongod: Image: registry.hub.docker.com/mongo:4.2.6 Port: <none> Host Port: <none> Command: /bin/sh -c #run post-start hook to handle version changes /hooks/version-upgrade # wait for config and keyfile to be created by the agent while ! [ -f /data/automation-mongod.conf -a -f /var/lib/mongodb-mms-automation/authentication/keyfile ]; do sleep 3 ; done ; sleep 2 ; # with mongod configured to append logs, we need to provide them to stdout as # mongod does not write to stdout and a log file tail -F /var/log/mongodb-mms-automation/mongodb.log > /dev/stdout & # start mongod with this configuration exec mongod -f /data/automation-mongod.conf; Limits: cpu: 1 memory: 500M Requests: cpu: 500m memory: 400M Environment: AGENT_STATUS_FILEPATH: /healthstatus/agent-health-status.json Mounts: /data from data-volume (rw) /healthstatus from healthstatus (rw) /hooks from hooks (rw) /var/lib/mongodb-mms-automation/authentication from example-mongodb-keyfile (rw) /var/log/mongodb-mms-automation from logs-volume (rw) mongodb-agent: Image: quay.io/mongodb/mongodb-agent:10.29.0.6830-1 Port: <none> Host Port: <none> Command: /bin/bash -c current_uid=$(id -u) declare -r current_uid if ! grep -q "${current_uid}" /etc/passwd ; then sed -e "s/^mongodb:/builder:/" /etc/passwd > /tmp/passwd echo "mongodb:x:$(id -u):$(id -g):,,,:/:/bin/bash" >> /tmp/passwd export NSS_WRAPPER_PASSWD=/tmp/passwd export LD_PRELOAD=libnss_wrapper.so export NSS_WRAPPER_GROUP=/etc/group fi agent/mongodb-agent -cluster=/var/lib/automation/config/cluster-config.json -healthCheckFilePath=/var/log/mongodb-mms-automation/healthstatus/agent-health-status.json -serveStatusPort=5000 -skipMongoStart -noDaemonize -useLocalMongoDbTools Limits: cpu: 1 memory: 500M Requests: cpu: 500m memory: 400M Readiness: exec [/opt/scripts/readinessprobe] delay=5s timeout=1s period=10s #success=1 #failure=40 Environment: AGENT_STATUS_FILEPATH: /var/log/mongodb-mms-automation/healthstatus/agent-health-status.json AUTOMATION_CONFIG_MAP: example-mongodb-config HEADLESS_AGENT: true POD_NAMESPACE: (v1:metadata.namespace) Mounts: /data from data-volume (rw) /opt/scripts from agent-scripts (rw) /var/lib/automation/config from automation-config (ro) /var/lib/mongodb-mms-automation/authentication from example-mongodb-keyfile (rw) /var/log/mongodb-mms-automation from logs-volume (rw) /var/log/mongodb-mms-automation/healthstatus from healthstatus (rw) Volumes: agent-scripts: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium: SizeLimit: <unset> automation-config: Type: Secret (a volume populated by a Secret) SecretName: example-mongodb-config Optional: false example-mongodb-keyfile: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium: SizeLimit: <unset> healthstatus: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium: SizeLimit: <unset> hooks: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium: SizeLimit: <unset> Volume Claims: Name: data-volume StorageClass: Labels: <none> Annotations: <none> Capacity: 10G Access Modes: [ReadWriteOnce] Name: logs-volume StorageClass: Labels: <none> Annotations: <none> Capacity: 2G Access Modes: [ReadWriteOnce] Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal SuccessfulCreate 3m53s statefulset-controller create Pod example-mongodb-0 in StatefulSet example-mongodb successful

…

On Tue, 22 Jun 2564 BE at 16:07 Nikolas De Giorgis ***@***.***> wrote: @Aonauma <https://github.com/Aonauma> can you please show me the output of kubectl describe deployment mongodb-kubernetes-operator and kubectl describe statefulset example-mongodb Please note that you will have to delete the pod that is failing to pull the image so that it gets rescheduled with the new image field and it should be able to pull from the right one — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#585 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGXLXVUSBB3SUUFVKU5TY3DTUBHE5ANCNFSM47DCETPA> .

[bznein]

Hi @Aonauma,

please next time format your output using the triple backtick (```).

Looking at your kubectl describe deployment output, it looks like you only changed MONGODB_IMAGE but not MONGODB_REPO_URL, which should be set to library for this workaround to work

[Aonauma]

Dear all, Thank you for help on that. I will try to change MONGODB_REPO_URL

…

On Tue, 22 Jun 2564 BE at 16:23 Nikolas De Giorgis ***@***.***> wrote: Hi @Aonauma <https://github.com/Aonauma>, please next time format your output using the triple backtick (```). Looking at your kubectl describe deployment output, it looks like you only changed MONGODB_IMAGE but not MONGODB_REPO_URL, which should be set to library for this workaround to work — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#585 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGXLXVTFZJDKMUQ6BGAYCOTTUBJBZANCNFSM47DCETPA> .