aws / aws/bedrock-agentcore-starter-toolkit
[BUG] --local-build fails even though docker is installed
- Dominant language
- Python
- Stars
- 508
- Forks
- 155
- Avg merge
- 8h 50m
- Merged PRs (30d)
- 4
Description
**Describe the bug**
Docker is installed but --local-build fails.
**To Reproduce**
```
agentcore launch --local-build
๐ง Launching Bedrock AgentCore (local-build mode - NEW!)...
โข Build container locally with Docker
โข Deploy to Bedrock AgentCore cloud runtime
โข Requires Docker/Finch/Podman to be installed
โข Use when you need custom build control
Using existing memory: ac_pg_mem-5sxtss21Ir
Using existing memory: ac_pg_mem-5sxtss21Ir
Launching Bedrock AgentCore agent 'ac_pg' to cloud
โ No supported container engine found.
AgentCore requires one of the following container engines for local builds:
โข Docker (any recent version, including Docker Desktop)
โข Finch (Amazon's open-source container engine)
โข Podman (compatible alternative to Docker)
To install:
โข Docker: https://docs.docker.com/get-docker/
โข Finch: https://github.com/runfinch/finch
โข Podman: https://podman.io/getting-started/installation
Alternative: Use CodeBuild for cloud-based building (no container engine needed):
agentcore launch # Uses CodeBuild (default)
which docker
/usr/bin/docker
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
```
**Expected behavior**
Is there a way to specify how to find docker?
**Error Output**
```
Paste any error messages or stack traces here
```
**Environment:**
uname -a
Linux ip-10-0-3-188 6.14.0-1011-aws #11~24.04.1-Ubuntu SMP Fri Aug 1 02:07:25 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
python --version
Python 3.12.3
(installed with pip in venv)
agentcore status
โ
MemoryManager initialized for region: us-west-2
๐ Retrieving memory resource with ID: ac_pg_mem-5sxtss21Ir...
Found memory: ac_pg_mem-5sxtss21Ir
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ Agent Status: ac_pg โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ โ ๏ธ Configured but not deployed โ
โ โ
โ Agent Details: โ
โ Agent Name: ac_pg โ
โ Region: us-west-2 โ
โ Account: XXXXX โ
โ โ
โ Configuration: โ
โ Execution Role: arn:aws:iam::125943838787:role/AmazonBedrockAgentCoreSDKRuntime-us-west-2-XXXXX โ
โ ECR Repository: 125943838787.dkr.ecr.us-west-2.amazonaws.com/bedrock-agentcore-ac_pg โ
โ โ
โ Your agent is configured but not yet launched. โ
โ โ
โ Next Steps: โ
โ agentcore launch โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
**Additional context**
Add any other context about the problem here.
Contributor guide
Research direction
Start by reproducing `agentcore launch --local-build` and compare its container-engine detection with `which docker` and `docker ps`. Trace the implementation behind the `--local-build` entry point; done means an installed Docker at `/usr/bin/docker` is recognized, or the supported way to specify its location is documented and works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100