devcontainer executable permissions.

Hey folks.

Thanks for this - it’s awesome!

I followed the instructions and enabled the devcontainer cli both on my Mac and on my Pop_OS linux machine. On both of these the devcontainer script was correctly symlinked into place, however calling devcontainer from a shell caused a permission denied error. Upon further inspection the ms-vscode-remote.remote-containers/cli-bin/devcontainer script was installed with 644 file permissions. I had to change them to 755 to be able to run it. Sadly, this means that I am getting an error about a corrupt vscode installation.

[chrmarti]

Not sure when this changed, but the code in Remote-Containers used to work as-is. I will chmod the file after copying as a fix in the extension.

[jrieken]

@jrieken when using vscode.workspace.fs we still go to the renderer process right?

It depends. When the file system is contributed by an extension (e.g. not the renderer, not the REH manager) than we short-circuit these request. So, the file and vscode-remote schemes should always be handled the “usual way” and not go the extension directly