Bug: Dev Container fails on macOS ARM64 due to architecture and network issues

[charliecheng630]

Environment:

• Dev Container: golang:1.24-bookworm
• Host: macOS on Apple Silicon (ARM64 / aarch64)
• Tools: VS Code + Remote - Containers + Docker Desktop

Problem / Observed Errors:

• kubectl version --client fails with Bus error
• curl downloads fail with PROTOCOL_ERROR
• Docker network creation fails if network kind already exists
• --network=host does not work on macOS Docker Desktop → Go module downloads fail

Impact:

• Apple Silicon (ARM64) users cannot successfully build the Dev Container.
• Current Dev Container scripts assume x86_64 Linux binaries and host network support → incompatible with macOS ARM64.

[2025-12-30T10:51:15.215Z] 
 66 55.8M   66 37.1M    0     0  55091      0  0:17:43  0:11:47  0:05:56  109k
[2025-12-30T10:51:16.274Z] 
 66 55.8M   66 37.2M    0     0  55170      0  0:17:42  0:11:48  0:05:54  110k
[2025-12-30T10:51:17.116Z] 
 77 55.8M   77 43.3M    0     0  64136      0  0:15:13  0:11:49  0:03:24 1348k
[2025-12-30T10:51:17.333Z] 
 79 55.8M   79 44.1M    0     0  65286      0  0:14:57  0:11:49  0:03:08 1783k
curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
[2025-12-30T10:51:17.354Z] + chmod +x kubectl
[2025-12-30T10:51:17.356Z] + mv kubectl /usr/local/bin/kubectl
[2025-12-30T10:51:17.461Z] + docker network create -d=bridge --subnet=172.19.0.0/24 kind
[2025-12-30T10:51:17.496Z] Error response from daemon: network with name kind already exists
[2025-12-30T10:51:17.496Z] + kind version
[2025-12-30T10:51:17.537Z] kind v0.32.0-alpha+81afcd0e84b596 go1.25.5 linux/amd64
[2025-12-30T10:51:17.538Z] + kubebuilder version
[2025-12-30T10:51:17.631Z] Version: cmd.version{KubeBuilderVersion:"4.10.1", KubernetesVendor:"1.34.1", GitCommit:"8bce950e46b914d54c872da25500b8c27b6c05e8", BuildDate:"2025-11-16T18:47:21Z", GoOs:"linux", GoArch:"amd64"}
[2025-12-30T10:51:17.631Z] + docker --version
[2025-12-30T10:51:17.641Z] Docker version 29.1.3-1, build f52814d454173982e6692dd7e290a41b828d9cbc
[2025-12-30T10:51:17.642Z] + go version
[2025-12-30T10:51:17.662Z] go version go1.24.11 linux/arm64
[2025-12-30T10:51:17.663Z] + kubectl version --client
[2025-12-30T10:51:17.664Z] .devcontainer/post-install.sh: line 23:  2823 Bus error               kubectl version --client
[2025-12-30T10:51:17.681Z] Stop (2099906 ms): Run in container: /bin/sh -c bash .devcontainer/post-install.sh
[2025-12-30T10:51:17.682Z] onCreateCommand from devcontainer.json failed with exit code 135. Skipping any further user-provided commands.
[2025-12-30T10:51:17.685Z] Error: Command failed: /bin/sh -c bash .devcontainer/post-install.sh
[2025-12-30T10:51:17.685Z]     at E (/Users/yuchen/.vscode/extensions/ms-vscode-remote.remote-containers-0.434.0/dist/spec-node/devContainersSpecCLI.js:235:157)
[2025-12-30T10:51:17.685Z]     at async Promise.allSettled (index 0)
[2025-12-30T10:51:17.685Z]     at async b9 (/Users/yuchen/.vscode/extensions/ms-vscode-remote.remote-containers-0.434.0/dist/spec-node/devContainersSpecCLI.js:237:119)
[2025-12-30T10:51:17.685Z]     at async ND (/Users/yuchen/.vscode/extensions/ms-vscode-remote.remote-containers-0.434.0/dist/spec-node/devContainersSpecCLI.js:226:4668)
[2025-12-30T10:51:17.685Z]     at async RD (/Users/yuchen/.vscode/extensions/ms-vscode-remote.remote-containers-0.434.0/dist/spec-node/devContainersSpecCLI.js:226:4013)
[2025-12-30T10:51:17.686Z]     at async MD (/Users/yuchen/.vscode/extensions/ms-vscode-remote.remote-containers-0.434.0/dist/spec-node/devContainersSpecCLI.js:226:3020)
[2025-12-30T10:51:17.686Z]     at async G7 (/Users/yuchen/.vscode/extensions/ms-vscode-remote.remote-containers-0.434.0/dist/spec-node/devContainersSpecCLI.js:668:2746)
[2025-12-30T10:51:17.686Z]     at async b7 (/Users/yuchen/.vscode/extensions/ms-vscode-remote.remote-containers-0.434.0/dist/spec-node/devContainersSpecCLI.js:667:8546)
[2025-12-30T10:51:17.686Z]     at async /Users/yuchen/.vscode/extensions/ms-vscode-remote.remote-containers-0.434.0/dist/spec-node/devContainersSpecCLI.js:484:1188
[2025-12-30T10:51:17.689Z] Stop (2100236 ms): Run: /private/var/folders/hr/_d5c23z929nd04690qhq3_140000gn/T/AppTranslocation/08F24227-FD19-45B7-890F-F9C5CE1AF199/d/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) /Users/yuchen/.vscode/extensions/ms-vscode-remote.remote-containers-0.434.0/dist/spec-node/devContainersSpecCLI.js run-user-commands --user-data-folder /Users/yuchen/Library/Application Support/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --container-session-data-folder /tmp/devcontainers-111cadcc-cbe3-4e69-b717-45d04816d0581767089683089 --workspace-folder /Users/yuchen/IdeaProjects/signalhound --id-label devcontainer.local_folder=/Users/yuchen/IdeaProjects/signalhound --id-label devcontainer.config_file=/Users/yuchen/IdeaProjects/signalhound/.devcontainer/devcontainer.json --container-id 569717731ff72eb39bcb091df588304683b21316e4a751788445af31e1ace0e1 --log-level debug --log-format json --config /Users/yuchen/IdeaProjects/signalhound/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --skip-non-blocking-commands true --prebuild false --stop-for-personalization true --remote-env REMOTE_CONTAINERS_IPC=/tmp/vscode-remote-containers-ipc-044513cf-ee24-4ac3-af65-e17b9ec36e53.sock --remote-env SSH_AUTH_SOCK=/tmp/vscode-ssh-auth-044513cf-ee24-4ac3-af65-e17b9ec36e53.sock --remote-env REMOTE_CONTAINERS=true --mount-workspace-git-root --dotfiles-target-path ~/dotfiles
[2025-12-30T10:51:17.690Z] Exit code 1
[2025-12-30T10:51:17.694Z] Command failed: /private/var/folders/hr/_d5c23z929nd04690qhq3_140000gn/T/AppTranslocation/08F24227-FD19-45B7-890F-F9C5CE1AF199/d/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) /Users/yuchen/.vscode/extensions/ms-vscode-remote.remote-containers-0.434.0/dist/spec-node/devContainersSpecCLI.js run-user-commands --user-data-folder /Users/yuchen/Library/Application Support/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --container-session-data-folder /tmp/devcontainers-111cadcc-cbe3-4e69-b717-45d04816d0581767089683089 --workspace-folder /Users/yuchen/IdeaProjects/signalhound --id-label devcontainer.local_folder=/Users/yuchen/IdeaProjects/signalhound --id-label devcontainer.config_file=/Users/yuchen/IdeaProjects/signalhound/.devcontainer/devcontainer.json --container-id 569717731ff72eb39bcb091df588304683b21316e4a751788445af31e1ace0e1 --log-level debug --log-format json --config /Users/yuchen/IdeaProjects/signalhound/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --skip-non-blocking-commands true --prebuild false --stop-for-personalization true --remote-env REMOTE_CONTAINERS_IPC=/tmp/vscode-remote-containers-ipc-044513cf-ee24-4ac3-af65-e17b9ec36e53.sock --remote-env SSH_AUTH_SOCK=/tmp/vscode-ssh-auth-044513cf-ee24-4ac3-af65-e17b9ec36e53.sock --remote-env REMOTE_CONTAINERS=true --mount-workspace-git-root --dotfiles-target-path ~/dotfiles
[2025-12-30T10:51:17.694Z] Exit code 1

[charliecheng630]

Root Cause:

• Binary architecture mismatch: Dev Container downloads amd64 binaries (kubectl, kind, kubebuilder), but container runs arm64 → Bus error.
• Host network unsupported on macOS Docker Desktop: causes curl / Go module downloads to fail.
• Docker network creation not idempotent: fails if kind network already exists.
• Missing required packages in minimal container: no curl or ca-certificates → HTTPS downloads fail.

I would like to work on this issue and provide a macOS / ARM64 compatible version of post-install.sh and updated devcontainer.json that:

• Detects architecture automatically
• Downloads correct binaries for kubectl, kind, and kubebuilder
• Uses bridge network on macOS
• Is safe to run on Linux x86_64 as well

I can submit a PR for review if maintainers are open to it.

[tico88612]

Go ahead, I can assist with the review.

[charliecheng630]

/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale