Question
Issues with do docker registry - 403 errors when building docker images from a gitlab pipeline Job
- Posted on February 18, 2021
- DigitalOcean Container Registry (DOCR)Kubernetes
Asked by ziiied
Hi,
I am having some intermitting issues building and pushing docker images (via CI gitlab job)
I am encountering this error:
error checking push permissions -- make sure you entered the correct tag name, and that you are authenticated correctly, and try again: checking push permission for "registry.digitalocean.com/redacted/redacted:latest":
creating push check transport for registry.digitalocean.com failed: GET https://registry.digitalocean.com/v2/:
unsupported status code 403;
body: <!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
<!--[if IE 7]> <html class="no-js ie7 oldie" lang="en-US"> <![endif]-->
<!--[if IE 8]> <html class="no-js ie8 oldie" lang="en-US"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]-->
<head>
<title>Attention Required! | Cloudflare</title>
...
Retrying seems “fixing” the issue…
I was not encountering this issue the last week. My CI builds started failing at the begging if the week.
Any idea ?
– Some more details:
- My gitlab runners are hosted on a DOKS cluster.
- Registry secrets were properly defined (It was flawlessly working the previous week)
- I am building images using Kaniko
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
I was able to resolve my issue by creating a new pool for my k8s cluster and removing the old pool.
But I am not able to understand what caused this issue
hi, maybe this will help you, this is how my pipeline is looking in gitlab (and is working fine):
$DO_REGISTRY_USER = $DO_REGISTRY_PASSWORD = API token from API in the DigitalOcean control panel