You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Run "Dev Containers: Add Dev Container Configuration Files..." and generate a .devcontainer/devcontainer.json
Run "Dev Containers: Rebuild and Reopen in Container"
Install Quarkus extension in the Dev Container
Run "Quarkus: Debug current Quarkus project"
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".
The text was updated successfully, but these errors were encountered:
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
mkdir 1
cd 1
quarkus create app org.acme:getting-started --extension=rest
code .
.devcontainer/devcontainer.json
"The terminal process failed to launch: Starting directory (cwd) "/getting-started" does not exist."
Workaround
Change the value of
options.cwd
intasks.json
from"getting-started"
to"${workspaceFolder}/getting-started"
.The text was updated successfully, but these errors were encountered: