Open ernestang98 opened 1 year ago
I also have the same issue, is there any update on this, other than go back to image dexidp/dex:v2.27.0
which does works
Normal Pulling 14m kubelet Pulling image "quay.io/argoproj/argocd:v2.6.5" Normal Pulled 14m kubelet Successfully pulled image "quay.io/argoproj/argocd:v2.6.5" in 1.258199581s Normal Pulling 12m (x4 over 14m) kubelet Pulling image "ghcr.io/dexidp/dex:v2.35.3" Warning Failed 12m (x4 over 14m) kubelet Failed to pull image "ghcr.io/dexidp/dex:v2.35.3": rpc error: code = Unknown desc = Error response from daemon: Head "https://ghcr.io/v2/dexidp/dex/manifests/v2.35.3": received unexpected HTTP status: 503 Service Unavailable Normal BackOff 12m (x5 over 14m) kubelet Back-off pulling image "ghcr.io/dexidp/dex:v2.35.3" Warning Failed 9m30s (x4 over 11m) kubelet Failed to pull image "ghcr.io/dexidp/dex:v2.35.2": rpc error: code = Unknown desc = Error response from daemon: Head "https://ghcr.io/v2/dexidp/dex/manifests/v2.35.2": received unexpected HTTP status: 503 Service Unavailable
This is definitely Github's issues. Check out https://www.githubstatus.com/ for any incidents currently happening.
Having the same issue but GH is 100% up
Some context:
kubectl get events -n argocd
4m14s Warning Failed pod/argocd-dex-server-b694449c5-spzc7 Failed to pull image "ghcr.io/dexidp/dex:v2.37.0": rpc error: code = Unknown desc = Error response from daemon: Head "https://ghcr.io/v2/dexidp/dex/manifests/v2.37.0": denied: denied
feel free to ask any details
Observed the same behavior when installing argocd in KinD cluster.
Was able to download the image using docker pull
.
As a workaround, edited the argocd manifest in local and updated the argocd-dex-server
deployment imagePullPolicy
from Always
to IfNotPresent
.
Deployed updated manifest, and manually uploaded the image to kind cluster using kind load docker-image ghcr.io/dexidp/dex:v2.38.0 --name <kind-cluster-name>
.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 14m default-scheduler Successfully assigned argocd/argocd-dex-server-7b6987df7-gt94p to argocd-control-plane
Warning Failed 13m kubelet Failed to pull image "quay.io/argoproj/argocd:v2.12.3": failed to pull and unpack image "quay.io/argoproj/argocd:v2.12.3": failed to copy: httpReadSeeker: failed open: unexpected status code https://quay.io/v2/argoproj/argocd/blobs/sha256:86749b599e3ed5b6879a0a72170d9585ed2876e43825874faea03d6ed12437ba: 502 Bad Gateway
Warning Failed 13m kubelet Error: ErrImagePull
Normal BackOff 13m kubelet Back-off pulling image "quay.io/argoproj/argocd:v2.12.3"
Warning Failed 13m kubelet Error: ImagePullBackOff
Normal Pulling 12m (x2 over 14m) kubelet Pulling image "quay.io/argoproj/argocd:v2.12.3"
Normal Pulled 11m kubelet Successfully pulled image "quay.io/argoproj/argocd:v2.12.3" in 8.682s (56.372s including waiting). Image size: 171926860 bytes.
Normal Created 11m kubelet Created container copyutil
Normal Started 11m kubelet Started container copyutil
Normal Pulling 10m (x3 over 11m) kubelet Pulling image "ghcr.io/dexidp/dex:v2.38.0"
Warning Failed 9m56s (x3 over 10m) kubelet Failed to pull image "ghcr.io/dexidp/dex:v2.38.0": failed to pull and unpack image "ghcr.io/dexidp/dex:v2.38.0": failed to resolve reference "ghcr.io/dexidp/dex:v2.38.0": failed to do request: Head "https://ghcr.io/v2/dexidp/dex/manifests/v2.38.0": tls: failed to verify certificate: x509: certificate signed by unknown authority
Warning Failed 9m56s (x3 over 10m) kubelet Error: ErrImagePull
Warning Failed 9m18s (x4 over 10m) kubelet Error: ImagePullBackOff
Normal BackOff 4m28s (x22 over 10m) kubelet Back-off pulling image "ghcr.io/dexidp/dex:v2.38.0"
Following this and many tutorials, I attempt to install argocd on minikube with a MacOS by running the following commands:
However, I encounter the following error with the dex-server as a result:
Running
kubectl describe pod/argocd-dex-server-5f9ffd8b4b-tmnzc -n argocd
, we observe:Running
kubectl get pod/argocd-dex-server-5f9ffd8b4b-tmnzc -o yaml -n argocd | grep image
, we observeChanging the image to
dexidp/dex:v2.27.0
seemed to fix it, maybe it is an issue with ghcr.io?