[BUG] I'm sorry to stir the pot for something that may not be a Documentation bug, but the VSCODE Readme doesn'

[kencottrell]

[BUG] I'm sorry to stir the pot for something that may not be a Documentation bug, but the VSCODE Readme doesn'

[olavt]

Yes, I have noticed the same problem. The documentation for how to set this up seems a bit outdated / incorrect.

I asked about this on Stackoverflow:

https://stackoverflow.com/questions/77570688/how-to-get-vs-code-devcontainer-to-execute-bash-command

I think the documentation / and or the initializeCommand should be improved to avoid everyone getting into the same issue.

[kencottrell]

@olavt can you think of any work arounds for this? I've tried all sorts of things to no avail. I guess it could be a problem with VSCode but I'd be ok with editing a config file and trying things out. Is there anyone on the CHIP team who would like to spend some time with me via zoom and work this out? I can document if needed

[olavt]

Editing the devcontainer.json file and change this line of code:

"initializeCommand": ".devcontainer/build.sh --tag matter-dev-environment:local --version 22"

to

"initializeCommand": "bash .devcontainer/build.sh --tag matter-dev-environment:local --version 22"

worked for me.

[kencottrell]

Thx olavt.

hmmm.

when I tried that I got a similar error message but now with "bash" passed as another argument to cmd.exe. Let me see if I can clear everything out and try again. I wonder if something is cached inside VS Code that needs to be cleared out.

[kencottrell]

I'm redoing this on my linux box and it appears successful. Still not sure why everyone can reset VSCode DevContainer windows to use bash vs. cmd and not me :-)