Dev Container configuration file already exists but is not being used

Open
#121 1 comment 0 reactions 2 assignees View on GitHub

@ryandanehy is already working on this.

Since Dec 16, 2023.

Assessment

This issue has not been assessed yet.

Description

bug documentation

Following the instructions on how to set up a dev container to develop ReSolve documentation, I ran out into an issue where vscode pops up a dialog box saying that json configuration file already exists for the dev container, but refuses to use it (there are 2 options none of which will run existing configuration). This issue seems to be a documented bug in vscode.

The workaround that get me pass this point was to add line like this

"initializeCommand": "ls"

at the end of devcontainer.json file. I don't know how and why, but it worked :P.

Dominant language
C++
Stars
85
Forks
14
PR merge metrics
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ORNL/ReSolve

All issues in ORNL/ReSolve

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.