If I launch a 0.21.0 KIND cluster it breaks docker run for some containers.
What happened:
Restart docker desktop (version v4.27.2), docker version (Docker version 25.0.3, build 4debf41)
Run command docker run gcr.io/k8s-staging-multitenancy/hnc-manager:v1.1.0
Command will run the container.
Now create a kind cluster: kind create cluster
Now try to run the container docker run gcr.io/k8s-staging-multitenancy/hnc-manager:v1.1.0 and there is an exec format error exec /manager: exec format error
After deleting the KIND cluster and restarting docker, the command docker run gcr.io/k8s-staging-multitenancy/hnc-manager:v1.1.0 can run again.
What you expected to happen:
Creating a KIND cluster does not introduce exec format errors for docker containers.
How to reproduce it (as minimally and precisely as possible):
docker run gcr.io/k8s-staging-multitenancy/hnc-manager:v1.1.0kind create clusterdocker run gcr.io/k8s-staging-multitenancy/hnc-manager:v1.1.0
Anything else we need to know?:
problem doesn't exist on kind 0.20.0
Environment:
kind version: (use kind version): 0.21.0
Runtime info: (use docker info or podman info):
Version: 25.0.3
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.12.1-desktop.4
Path: /Users/igorvelichkovich/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.24.5-desktop.1
Path: /Users/igorvelichkovich/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container. (Docker Inc.)
Version: 0.0.24
Path: /Users/igorvelichkovich/.docker/cli-plugins/docker-debug
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: /Users/igorvelichkovich/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.21
Path: /Users/igorvelichkovich/.docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.4
Path: /Users/igorvelichkovich/.docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.0.0
Path: /Users/igorvelichkovich/.docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /Users/igorvelichkovich/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.4.1
Path: /Users/igorvelichkovich/.docker/cli-plugins/docker-scout
If I launch a 0.21.0 KIND cluster it breaks docker run for some containers.
What happened:
Restart docker desktop (version v4.27.2), docker version (Docker version 25.0.3, build 4debf41) Run command
docker run gcr.io/k8s-staging-multitenancy/hnc-manager:v1.1.0
Command will run the container. Now create a kind cluster:kind create cluster
Now try to run the containerdocker run gcr.io/k8s-staging-multitenancy/hnc-manager:v1.1.0
and there is an exec format errorexec /manager: exec format error
After deleting the KIND cluster and restarting docker, the command
docker run gcr.io/k8s-staging-multitenancy/hnc-manager:v1.1.0
can run again.What you expected to happen:
Creating a KIND cluster does not introduce exec format errors for docker containers.
How to reproduce it (as minimally and precisely as possible):
docker run gcr.io/k8s-staging-multitenancy/hnc-manager:v1.1.0
kind create cluster
docker run gcr.io/k8s-staging-multitenancy/hnc-manager:v1.1.0
Anything else we need to know?:
problem doesn't exist on kind 0.20.0
Environment:
kind version
): 0.21.0docker info
orpodman info
):Server: Containers: 71 Running: 1 Paused: 0 Stopped: 70 Images: 5 Server Version: 25.0.3 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb runc version: v1.1.12-0-g51d5e94 init version: de40ad0 Security Options: seccomp Profile: unconfined cgroupns Kernel Version: 6.6.12-linuxkit Operating System: Docker Desktop OSType: linux Architecture: aarch64 CPUs: 12 Total Memory: 7.657GiB Name: docker-desktop ID: d90cceb7-44ff-4f92-a8e8-2494e0d2708b Docker Root Dir: /var/lib/docker Debug Mode: false HTTP Proxy: http.docker.internal:3128 HTTPS Proxy: http.docker.internal:3128 No Proxy: hubproxy.docker.internal Experimental: false Insecure Registries: hubproxy.docker.internal:5555 127.0.0.0/8 Live Restore Enabled: false
WARNING: daemon is not using the default seccomp profile```
/etc/os-release
): Mac OS 14.3.1 (23D60)kubectl version
): default kind cluster version, 1.29