Summary
User is experiencing an error when trying to pull a custom Docker image in a Kubernetes pipeline, indicating insufficient access or authorization issues.
Question
Hi, Help please, stuck on this
I am able to add custom connector on kubernetes and i added the secret and assigned to JOB_KUBE_MAIN_CONTAINER_IMAGE_PULL_SECRET
but when i create pipeline on kubernetes-check pod is coming up and giving error. <@U035912NS77>
Failed to pull image "advent/kubernetes-images:cutomDev": failed to pull and unpack image "<http://docker.io/advent/kubernetes-images:cutomDev|docker.io/advent/kubernetes-images:cutomDev>": failed to resolve reference "<http://docker.io/advent/kubernetes-images:cutomDev|docker.io/advent/kubernetes-images:cutomDev>": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
['kubernetes', 'image-pull', 'docker', 'authorization', 'custom-connector']
You have a typo there: cutomDev, should it be customDev instead?
This is just name for masking purpose, no typo issue.
first issue i got when adding custom connecter same error it was picking the JOB_KUBE_MAIN_CONTAINER_IMAGE_PULL_SECRET properly once i added when i am able to add the connector now when i run the connection i am getting the above issue.
i updated the following in the helm chart.
add this in env of worker
JOB_KUBE_MAIN_CONTAINER_IMAGE_PULL_SECRET
updated this for jobs
main_container_image_pull_secret:“secretAirbyte”
<@U065RJ879QT> <@U06EADEMRNZ>
You have a typo there: cutomDev, should it be customDev instead?
This is just name for masking purpose, no typo issue.
first issue i got when adding custom connecter same error it was picking the JOB_KUBE_MAIN_CONTAINER_IMAGE_PULL_SECRET properly once i added when i am able to add the connector now when i run the connection i am getting the above issue.
i updated the following in the helm chart.
add this in env of worker
JOB_KUBE_MAIN_CONTAINER_IMAGE_PULL_SECRET
updated this for jobs
main_container_image_pull_secret:“secretAirbyte”
<@U065RJ879QT> <@U06EADEMRNZ>