You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cr.step.sm docker registry cannot be resolved anymore as of Aug 28th, all pods are failing on pulling both the autocert-bootstrapper and autocert-renewer images.
Environment
Kubernetes version: 1.28.9
Cloud provider or hardware configuration: AKS
OS (e.g., from /etc/os-release): Irrelevant
Kernel (e.g., uname -a): Irrelevant
Install tools:
Other:
Steps to reproduce
Run docker pull cr.step.sm/smallstep/autocert-bootstrapper:0.16.0
Expected behaviour
Docker image is pulled successfully
Actual behaviour
Error response from daemon: Get "https://cr.step.sm/v2/": dialing cr.step.sm:443 with direct connection: resolving host cr.step.sm: lookup cr.step.sm: no such host
The text was updated successfully, but these errors were encountered:
Subject of the issue
cr.step.sm docker registry cannot be resolved anymore as of Aug 28th, all pods are failing on pulling both the
autocert-bootstrapper
andautocert-renewer
images.Environment
uname -a
): IrrelevantSteps to reproduce
Run
docker pull cr.step.sm/smallstep/autocert-bootstrapper:0.16.0
Expected behaviour
Docker image is pulled successfully
Actual behaviour
Error response from daemon: Get "https://cr.step.sm/v2/": dialing cr.step.sm:443 with direct connection: resolving host cr.step.sm: lookup cr.step.sm: no such host
The text was updated successfully, but these errors were encountered: