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
Using containerd as container runtime, docker pull image (and docker run) ignores the insecure registry defined on daemon.json. This makes unusable registry with HTTP or HTTPS with self-signed or invalid certificate.
Reproduce
Configure Docker to use containerd as container runtime (check Settings -> General -> Use containerd for pulling and storing images)
Define at least an insecure registry on ~/.docker/daemon.json or by Docker Desktop on Setting -> Docker Engine like below:
Other issue talks about issue with Buildkit. I have tried to disable it but issue remains.
The only way to currently execute docker pull with insecure registry is to do disable containerd as container runtime.
The text was updated successfully, but these errors were encountered:
I have a similar issue configuring client certificates for a private registry. It works when not using containerd, by copying the certs.d from the users home to the VM it seems as per https://docs.docker.com/desktop/faqs/macfaqs/#add-client-certificates, however I can't find a way to make this work with containerd enabled.
Description
Using
containerd
as container runtime, docker pull image (and docker run) ignores the insecure registry defined ondaemon.json
. This makes unusable registry with HTTP or HTTPS with self-signed or invalid certificate.Reproduce
~/.docker/daemon.json
or by Docker Desktop on Setting -> Docker Engine like below:Expected behavior
docker pull
successfully store the image into local registry.docker version
Client: Version: 27.2.0 API version: 1.47 Go version: go1.21.13 Git commit: 3ab4256 Built: Tue Aug 27 14:14:45 2024 OS/Arch: darwin/arm64 Context: desktop-linux Server: Docker Desktop 4.34.2 (167172) Engine: Version: 27.2.0 API version: 1.47 (minimum version 1.24) Go version: go1.21.13 Git commit: 3ab5c7d Built: Tue Aug 27 14:15:41 2024 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.7.20 GitCommit: 8fc6bcff51318944179630522a095cc9dbf9f353 runc: Version: 1.1.13 GitCommit: v1.1.13-0-g58aa920 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Diagnostics ID
77121D55-FED5-4309-99F9-434930CBAEF6/20241006101557
Additional Info
Other issue talks about issue with Buildkit. I have tried to disable it but issue remains.
The only way to currently execute
docker pull
with insecure registry is to do disablecontainerd
as container runtime.The text was updated successfully, but these errors were encountered: