-
Notifications
You must be signed in to change notification settings - Fork 6
Installation: docker image inspect fails #1
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Component
CDK / infrastructure
Describe the bug
Following the installation guide (https://github.com/aws-samples/sample-autonomous-cloud-coding-agents/blob/main/docs/guides/DEVELOPER_GUIDE.md), I cloned the repository and ran through the steps up through running the initial build:
npx projen install
npx projen build
While running those commands, I got this error:
[security:image] $ docker image inspect bgagent-local:latest >/dev/null 2>&1 || (ARCH="$(uname -m)"; PLATFORM="linux/arm64"; if [ "$ARCH" = "x86_64" ]; then PLATFORM="linux/amd64"; fi; do…
[+] Building 66.0s (5/5) FINISHED docker:desktop-linux
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 2.76kB 0.0s
=> WARN: RedundantTargetPlatform: Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior (line 3) 0.0s
=> WARN: RedundantTargetPlatform: Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior (line 5) 0.0s
=> ERROR [internal] load metadata for docker.io/jdxcode/mise:latest 66.0s
=> [internal] load metadata for ghcr.io/astral-sh/uv:latest 10.3s
=> [internal] load metadata for docker.io/library/python:3.13-slim 9.9s
=> [auth] library/python:pull token for registry-1.docker.io 0.0s
------
> [internal] load metadata for docker.io/jdxcode/mise:latest:
------
2 warnings found (use docker --debug to expand):
- RedundantTargetPlatform: Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior (line 3)
- RedundantTargetPlatform: Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior (line 5)
Dockerfile:3
--------------------
1 | ARG TARGETPLATFORM=linux/arm64
2 |
3 | >>> FROM --platform=$TARGETPLATFORM jdxcode/mise:latest AS mise
4 |
5 | FROM --platform=$TARGETPLATFORM python:3.13-slim
--------------------
ERROR: failed to build: failed to solve: jdxcode/mise:latest: failed to resolve source metadata for docker.io/jdxcode/mise:latest: failed to do request: Head "https://registry-1.docker.io/v2/jdxcode/mise/manifests/latest": EOF
View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/irphjlv40kve8lpngymep5fbo
[security:image] ERROR task failed
👾 Task "build » post-compile » agent:check" failed when executing "mise run security" (cwd: /Users/<uid>/Documents/sample-autonomous-cloud-coding-agents/agent)
I used an AI coding tool to debug, and it suggested I make this change:
diff --git a/agent/Dockerfile b/agent/Dockerfile
index d0d52e8..1ebb9c5 100644
--- a/agent/Dockerfile
+++ b/agent/Dockerfile
@@ -1,12 +1,7 @@
ARG TARGETPLATFORM=linux/arm64
-FROM --platform=$TARGETPLATFORM jdxcode/mise:latest AS mise
-
FROM --platform=$TARGETPLATFORM python:3.13-slim
-# Install mise (polyglot dev tool manager)
-COPY --from=mise /usr/local/bin/mise /usr/local/bin/mise
-
# Install system dependencies in a single layer:
# - Node.js 20 (required by Claude Code CLI)
# - git (repo operations)
@@ -20,6 +15,8 @@ RUN apt-get update && \
build-essential \
ca-certificates \
gnupg && \
+ # Install mise (polyglot dev tool manager)
+ curl -fsSL https://mise.run | MISE_INSTALL_PATH=/usr/local/bin/mise sh && \
# Node.js 20
curl -fsSL https://deb.nodesource.com/setup_20.x | bash - && \
apt-get install -y --no-install-recommends nodejs && \
That appeared to work for me, but I am not sure if this is the correct approach.
Expected behavior
Initial install and build steps works.
Current behavior
Initial install and build fails.
Reproduction steps
Clone repo and go through installation guide up through initial install and build.
Possible solution
See suggested diff patch in description.
Node version
v24.13.0
Python version
Python 3.13.9
mise version
2026.4.0 macos-arm64 (2026-04-01)
AWS region
us-west-2
Local modifications
No response
Additional context
No response
AWS quotas
- I have reviewed the relevant service quotas (or N/A)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working