`up`  hangs indefinitely when the container start event is missed (warm daemon + cached image)

Open
#1,269 1 comment 0 reactions 1 assignee View on GitHub

@v-Kaniska244 is already working on this.

Since Jul 24, 2026.

Assessment

This issue has not been assessed yet.

Description

What happened
On a warm Docker daemon with an already-built/cached image,  devcontainer up occasionally hangs forever. The container is created and running, but the CLI never proceeds to the lifecycle hooks.

Root cause
In  spawnDevContainer ,  startEventSeen  spawns docker events --filter event=start and then docker run follows almost immediately. With a cached image the container starts before the events listener has finished subscribing, so the start event is missed and awaited indefinitely.

Impact
 up hangs with no timeout; lifecycle hooks ( onCreate / postCreate / postStart ) never run.

Environment

•  @devcontainers/cli : 0.60.0
• Docker Engine: 29.6.1 (API 1.55), backend linux/amd64
• Node.js: v24.12.0 (from your Output pane), host Windows 10.0.26100

• Repro: warm daemon, image already cached, then  devcontainer up

Dominant language
TypeScript
Stars
3k
Forks
461
Avg merge
18m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

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

More from devcontainers/cli

All issues in devcontainers/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.