devcontainers using docker-compose can't find Dockerfile
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 42/100
Línea de trabajo
Comienza con .devcontainer/devcontainer.json y docker-compose.yml, y luego reproduce el fallo utilizando la configuración de Podman/VS Code Flatpak descrita en el registro. Compara la ruta del Dockerfile que ve podman-compose con la estructura del proyecto y determina si está implicado el sandbox de Flatpak; se considera terminado cuando se hayan establecido la causa y una corrección reproducible o un workaround documentado.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
I have a project that has an existing docker-compose.yml that I'd like to use. This docker-compose.yml runs a service built from a local Dockerfile, referenced as follows:
build:
dockerfile: "Dockerfile"
context: .
My .devcontainer/devcontainer.json is as follows:
{
"name": "<project name>",
"dockerComposeFile": "../docker-compose.yml",
"service": "<service in docker-compose>",
"workspaceFolder": "/app",
"shutdownAction": "stopCompose"
}
Opening VSCode using this seemingly simple setup however fails:
[2024-10-18T13:35:07.085Z] Traceback (most recent call last):
File "/usr/bin/podman-compose", line 8, in <module>
[2024-10-18T13:35:07.085Z] sys.exit(main())
^^^^^^
File "/usr/lib/python3.12/site-packages/podman_compose.py", line 3504, in main
[2024-10-18T13:35:07.086Z] asyncio.run(async_main())
File "/usr/lib/python3.12/asyncio/runners.py", line 194, in run
return runner.run(main)
^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/asyncio/runners.py", line 118, in run
[2024-10-18T13:35:07.086Z] return self._loop.run_until_complete(task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/podman_compose.py", line 3500, in async_main
[2024-10-18T13:35:07.086Z] await podman_compose.run()
File "/usr/lib/python3.12/site-packages/podman_compose.py", line 1743, in run
[2024-10-18T13:35:07.087Z] retcode = await cmd(self, args)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/podman_compose.py", line 2422, in compose_build
s = await t
^^^^^^^
File "/usr/lib/python3.12/asyncio/tasks.py", line 631, in _wait_for_one
return f.result() # May raise f.exception().
^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/podman_compose.py", line 2373, in build_one
[2024-10-18T13:35:07.087Z] raise OSError("Dockerfile not found in " + ctx)
[2024-10-18T13:35:07.087Z] OSError: Dockerfile not found in /home/<user>/<project>
[2024-10-18T13:35:07.115Z] Error: executing /usr/bin/podman-compose --project-name <project name> -f /home/<user>/<project>/docker-compose.yml -f /home/<user>/.var/app/com.visualstudio.code/config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data/docker-compose/docker-compose.devcontainer.build-1729258506835.yml build: exit status 1
[2024-10-18T13:35:07.123Z] Stop (287 ms): Run: /home/<user>/.local/bin/podman-host compose --project-name <project name> -f /home/<user>/<project>/docker-compose.yml -f /home/<user>/.var/app/com.visualstudio.code/config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data/docker-compose/docker-compose.devcontainer.build-1729258506835.yml build
[2024-10-18T13:35:07.126Z] Error: Command failed: /home/<user>/.local/bin/podman-host compose --project-name <project name> -f /home/<user>/<project>/docker-compose.yml -f /home/<user>/.var/app/com.visualstudio.code/config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data/docker-compose/docker-compose.devcontainer.build-1729258506835.yml build
[2024-10-18T13:35:07.126Z] at Pm (/home/<user>/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-containers-0.388.0/dist/spec-node/devContainersSpecCLI.js:430:525)
[2024-10-18T13:35:07.126Z] at async ftA (/home/<user>/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-containers-0.388.0/dist/spec-node/devContainersSpecCLI.js:430:2476)
[2024-10-18T13:35:07.126Z] at async htA (/home/<user>/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-containers-0.388.0/dist/spec-node/devContainersSpecCLI.js:410:3496)
[2024-10-18T13:35:07.126Z] at async TtA (/home/<user>/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-containers-0.388.0/dist/spec-node/devContainersSpecCLI.js:482:4021)
[2024-10-18T13:35:07.126Z] at async iB (/home/<user>/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-containers-0.388.0/dist/spec-node/devContainersSpecCLI.js:482:4963)
[2024-10-18T13:35:07.126Z] at async wrA (/home/<user>/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-containers-0.388.0/dist/spec-node/devContainersSpecCLI.js:663:203)
[2024-10-18T13:35:07.126Z] at async DrA (/home/<user>/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-containers-0.388.0/dist/spec-node/devContainersSpecCLI.js:662:14830)
[2024-10-18T13:35:07.127Z] at async /home/<user>/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-containers-0.388.0/dist/spec-node/devContainersSpecCLI.js:482:1190
[2024-10-18T13:35:07.143Z] Stop (1298 ms): Run: /app/extra/vscode/code /home/<user>/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-containers-0.388.0/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /home/<user>/.var/app/com.visualstudio.code/config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --docker-path /home/<user>/.local/bin/podman-host --container-session-data-folder /tmp/devcontainers-1248c3b6-2a23-4114-a0b8-e99fac641c2c1729258504414 --workspace-folder /home<user>/<project> --workspace-mount-consistency cached --gpu-availability detect --id-label devcontainer.local_folder=/home/<user>/<project> --id-label devcontainer.config_file=/home/<user>/<project>/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/<user>/<project>/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root --include-configuration --include-merged-configuration
[2024-10-18T13:35:07.143Z] Exit code 1
[2024-10-18T13:35:07.151Z] Command failed: /app/extra/vscode/code /home/<user>/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode-remote.remote-containers-0.388.0/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /home/<user>/.var/app/com.visualstudio.code/config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --docker-path /home/<user>/.local/bin/podman-host --container-session-data-folder /tmp/devcontainers-1248c3b6-2a23-4114-a0b8-e99fac641c2c1729258504414 --workspace-folder /home/<user>/<project> --workspace-mount-consistency cached --gpu-availability detect --id-label devcontainer.local_folder=/home/<user>/<project> --id-label devcontainer.config_file=/home/<user>/<project>/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/<user>/<project>/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root --include-configuration --include-merged-configuration
[2024-10-18T13:35:07.151Z] Exit code 1
OSError: Dockerfile not found in /home/<user>/<project> seems weird to me, because the Dockerfile is there. Outside of VSCode and Flatpak and what not I can build this Docker (well, Podman really) setup just fine, so I'm guessing the Flatpak sandbox is in the way somehow?
- Lenguaje dominante
- Shell
- Estrellas
- 218
- Forks
- 79
- Merge medio
- 4 d 12 h
- PR fusionados (30 d)
- 3
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de flathub/com.visualstudio.code
-
Document podman/dockerAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
flathub/com.visualstudio.code#679 · 4 comentarios ·
-
App logs to stderr "Warning: 'ms-enable-electron-run-as-node' is not in the list of known options, but still passed to Electron/Chromium."Quizá libre de nuevo Un pull request para esta issue se cerró sin fusionarse. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 65/100
flathub/com.visualstudio.code#563 · 2 reacciones ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
flathub/com.visualstudio.code#388 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 55/100
flathub/com.visualstudio.code#715 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
flathub/com.visualstudio.code#710 ·
Todos los issues de flathub/com.visualstudio.code
Issues similares
-
Set wallpaperAbiertonew-addition
Dificultad 1/5 Menos de una hora Aptitud para principiantes 60/100
-
needs-triage Platform(Default)
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
winapps-org/winapps#984 ·
-
Bluetooth can't be turned back on from the bar on ThinkPads: rfkill block removes the adapterAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
[Linux] --calibrate combined with --model silently falls through to plain re-setup (setup.py:4958)Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día