without "bash" at the start of this command, the devcontainer machinery invokes "sh -c ./.devcontainer/updateContent.sh".
But this file is not executable, so we get a permissions denied error. Changing the command to
bash ./.devcontainer/updateContent.sh
tells the build machinery to invoke bash (which is executable) and use it to read and execute the specified script. Since updateContent.sh is readable, and since bash is executable, the build machinery is able to run the updateContentCommand script this way.
I should have marked the file as executable, but maybe editing on Windows messed things up. Invoking it with bash should work even if somebody downloads the source in a zip file so it's probably better.
without "bash" at the start of this command, the devcontainer machinery invokes "sh -c ./.devcontainer/updateContent.sh".
But this file is not executable, so we get a permissions denied error. Changing the command to
tells the build machinery to invoke
bash
(which is executable) and use it to read and execute the specified script. SinceupdateContent.sh
is readable, and sincebash
is executable, the build machinery is able to run theupdateContentCommand
script this way.see https://github.com/gurumitts/pylutron-caseta/issues/158