Dev Container configuration file already exists but is not being used

[pelesh]

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.

[cameronrutherford]

I was able to repro something similar on my Windows box for a different project and it occured to me that my current workaround is to Open Folder outside of a container first.

Maybe this is a feature, not a bug per the issue you linked.