Error when run build task inside a Dev Container

Summary

When using a Dev Container or a remote environment, if a Quarkus project is located in a subdirectory, the tasks in the launch.json file generated by the Quarkus extension fail to execute.

Repro steps

1. mkdir 1
2. cd 1
3. quarkus create app org.acme:getting-started --extension=rest
4. code .
5. Open Command Palette
6. Run "Dev Containers: Add Dev Container Configuration Files..." and generate a .devcontainer/devcontainer.json
7. Run "Dev Containers: Rebuild and Reopen in Container"
8. Install Quarkus extension in the Dev Container
9. Run "Quarkus: Debug current Quarkus project"
10. The task failed to execute with the following error:
    "The terminal process failed to launch: Starting directory (cwd) "/getting-started" does not exist."

Workaround

Change the value of options.cwd in tasks.json from "getting-started" to "${workspaceFolder}/getting-started".

Reproduce the issue with the listed Dev Container steps, then inspect the generated launch.json and tasks.json, especially options.cwd. Confirm the fix by checking that the generated task uses the workspace-relative project path and that “Quarkus: Debug current Quarkus project” runs successfully inside the container.