[Bug]: devcontainer post-create.sh fails on Kiro CLI 404, blocking uv, DocFx, Kimi and CodeBuddy installs

Open Beginner friendly

#2,605 opened on May 16, 2026 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 75/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Active
Tech stack: docker, shell
Domain: devops, tooling

Research direction

Start with post-create.sh and the postCreateCommand in devcontainer.json, then reproduce the container setup to observe the Kiro CLI 404. Ensure a failed Kiro installation does not prevent uv, DocFx, Kimi CLI, and CodeBuddy from being installed. Confirm completion by rebuilding the dev container and checking that the later tools are available.

Written by the indexing model from the issue text.

Description

stale

Bug Description

The post-create.sh script exits early when Kiro CLI installation fails with a 404 error, everything after Kiro is never installed: uv, DocFx, Kimi CLI, and CodeBuddy.

Steps to Reproduce

Clone spec-kit
Open in VS Code → "Dev Containers: Open Folder in Container..."
Wait for container build to complete

Expected Behavior

All tools defined in post-create.sh are installed, even if Kiro CLI installation fails.

Actual Behavior

The script stops at Kiro CLI and never installs uv, DocFx, Kimi CLI, and CodeBuddy.

Specify CLI Version

uv not installed ...

AI Agent

Not applicable

Operating System

macos 26.5

Python Version

uv was never installed due to this bug

Error Logs

🤖 Installing Kiro CLI...
[ERROR] Command failed (Exit Code 22): curl -fsSL "https://kiro.dev/install.sh" -o "/tmp/tmp.IxPtRpp6RF"
curl: (22) The requested URL returned error: 404
[468580 ms] postCreateCommand from devcontainer.json failed with exit code 22. Skipping any further user-provided commands.

Additional Context

Confirmed the issue is not network-related:

vscode ➜ /workspaces/spec-kit (main) $ curl -fsSL "https://kiro.dev/install.sh" -o /tmp/test-kiro.sh; echo "Exit code: $?"
curl: (22) The requested URL returned error: 404
Exit code: 22
vscode ➜ /workspaces/spec-kit (main) $ curl -fsSL "https://google.com" -o /dev/null && echo "OK"
OK

Dominant language: Python
Stars: 138k
Forks: 12.4k
Avg merge: 3d 6h
Merged PRs (30d): 136

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[BUG] GkeTpuCluster queries metadata.google.internal for MEGASCALE_SLICE_ID even when TPU_SKIP_MDS_QUERY is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

jax-ml/jax#40854 · Opened Sep 22, 2026
[pcied] Honour PCIE_DETACH_INFO on platforms that are not smartswitches Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

sonic-net/sonic-platform-daemons#900 · Opened Sep 21, 2026
MCP client has no httpx timeout, so the event stream fails after 5 seconds Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

Azure/azure-functions-agents-runtime#228 · Opened Sep 21, 2026
feat(mcp): friendlier error when `run_cloud_sync` is called on a disabled connection Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

airbytehq/PyAirbyte#1205 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026

More Python issues