`up` hangs after "Container started" when creating a container with Podman on Windows (podman machine / WSL)

Abierto
  • ¿Algo no está bien?
#1,355 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
54/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
node.js, typescript
Área
backend, devtools

Línea de trabajo

Start by comparing the container creation path with the existing Podman hang reported in #1236, then trace what the CLI does after logging "Container started" on Windows with Podman. The report provides no source files or tests, so locate the creation flow and its tests from that log point. Done when a fresh container creation completes and the CLI proceeds to connect, including on Podman machine backed by WSL2.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

With Podman as container engine on Windows, creating a dev container never finishes: the log stops right after Container started, and nothing else is logged. The container itself is running (podman ps -a shows Up, podman inspect shows State.Running=true).

This looks like the same symptom as #1236 (hang after "Container started" on create/recreate with Podman), but on Windows with a Podman machine instead of Linux.

Environment
  • OS: Windows 11 Pro 26H2 (win32 10.0.26300 x64), Podman machine backed by WSL2
  • VS Code 1.145.2, Dev Containers extension 0.469.0, @devcontainers/cli 0.89.0 (Node v24.22.1)
  • Podman client 6.1.4 / server 6.0.2, buildah 1.45.2
  • dev.containers.dockerPath / --docker-path: podman
devcontainer.json
{
  "name": "Dev env",
  "image": "node:24-slim",
  "remoteUser": "node"
}
Steps to reproduce
  1. Open a folder with the devcontainer.json above in VS Code, with no previous containers or volumes for it.
  2. Run "Dev Containers: Reopen in Container".
  3. The window stays on "Starting container" indefinitely.

Reproducible every time on container creation: first build, "Rebuild Container" and "Rebuild Container Without Cache" all end in the same hang, even when no previous containers or volumes exist.

Workaround

Force-close the remote connection and run "Reopen in Container" again (normal, no rebuild). Since the container is already built, it starts without any problem and VS Code connects normally (in the successful log the CLI runs podman start on the existing container, inspects it and installs the VS Code Server).

Related
  • #1236
Lenguaje dominante
TypeScript
Estrellas
3k
Forks
475
Merge medio
10 h 31 min
PR fusionados (30 d)
9

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de devcontainers/cli

Todos los issues de devcontainers/cli

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.