Skip to content
This repository has been archived by the owner on Apr 7, 2023. It is now read-only.

Launch with docker-compose in Codespaces / VSCode does not work #21

Open
wulfland opened this issue Oct 16, 2022 · 1 comment
Open

Launch with docker-compose in Codespaces / VSCode does not work #21

wulfland opened this issue Oct 16, 2022 · 1 comment

Comments

@wulfland
Copy link
Member

The docker-compose up as a prelaunch does not work in Codespaces / VSCode. I think the debuggerPath and containerName are missing in .vscode/launch.json:

        {
            "name": "Docker (start Frontend)",
            "type": "docker",
            "request": "attach",
            "preLaunchTask": "docker compose up",
            "postDebugTask": "docker compose down",
            "platform": "netCore",
            "containerName": "start-leaderboardwebapi-1",
            "netCore": {
                "debuggerPath": "/remote_debugger/vsdbg" // This is the path to vsdbg in the container
            },
            "sourceFileMap": {
                "/src": "${workspaceFolder}/start"
            }
        }
@loekd
Copy link
Contributor

loekd commented Oct 18, 2022

This is true, but i.m.o. due to a bug in VS Code.
Omitting the debugger path triggers a download during launch.
Omitting the container name triggers a question.

Our workaround is to manually run the docker compose up task, and then launch this one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants