Before submitting
What happened?
When using the microsandbox provider, I'm unable to open a functional workspace with vscode.
What did you expect to happen instead?
The sandbox opens and is functional.
Steps to reproduce
- Ensure msb is installed and latest version (available on local PATH)
- Setup microsandbox provider using all default values in Devsy
- Create a new Workspace using any of the example repo's as a test
- The launch will come back successful and vscode will open.
- Select Linux as the remote host type in vscode
- Trust the workspace
- From here on out, it doesn't work. Below is just the steps I've tried to see what happens.
- Receive the error - "Workspace does not exist". Select "Open Workspace...". Navigate to /workspaces as the root instead of /workspaces/<example_repo_name> (Doesn't seem to be possible to select the repo itself as the root). Hit OK.
- Trust the folder again. Recieve an ssh timeout, but reconnect again.
- You'll now be in the workspace and can see the repo and its files. But no files will be openable. The terminal seems to work.
devcontainer.json
Error output / logs
[error] [Window] Error: Unable to read file 'vscode-remote://ssh-remote+node.devsy/workspaces/node/.vscode/launch.json' (Unknown (FileSystemError): Error: ELOOP: too many symbolic links encountered, stat '/workspaces/node/.vscode/launch.json')
Same thing later on when using /workspace as the root and trying to open a file:
[error] [Window] Error: Unable to read file 'vscode-remote://ssh-remote+node.devsy/workspaces/node/LICENSE' (Unknown (FileSystemError): Error: ELOOP: too many symbolic links encountered, stat '/workspaces/node/LICENSE')
How often does this happen?
Every time
Operating system
Windows
Linux distribution (if applicable)
No response
Architecture
AMD64
Desktop app or CLI?
Desktop app
Devsy version
v1.17.0
Devsy provider
microsandbox
Provider version
v1.0.0
Screenshots
Anything else?
File ownership doesn't seem to be an issue:
node ➜ /workspaces $ ls -la /workspaces/
total 12
drwxr-xr-x 3 node node 4096 Jan 1 2020 .
drwxr-xr-x 1 root root 4096 Jan 1 2020 ..
drwxrwxrwx 1 node node 4096 Sep 8 17:27 node
node ➜ /workspaces $ ls -la /workspaces/node
total 62
drwxrwxrwx 1 node node 4096 Sep 8 17:27 .
drwxr-xr-x 3 node node 4096 Jan 1 2020 ..
-rwxrwxrwx 1 node node 444 Sep 8 17:27 CODE_OF_CONDUCT.md
drwxrwxrwx 1 node node 0 Sep 8 17:27 .devcontainer
-rwxrwxrwx 1 node node 328 Sep 8 17:27 .eslintrc.json
drwxrwxrwx 1 node node 4096 Sep 8 17:27 .git
-rwxrwxrwx 1 node node 89 Sep 8 17:27 .gitattributes
drwxrwxrwx 1 node node 0 Sep 8 17:27 .github
-rwxrwxrwx 1 node node 5598 Sep 8 17:27 .gitignore
-rwxrwxrwx 1 node node 1183 Sep 8 17:27 LICENSE
-rwxrwxrwx 1 node node 284 Sep 8 17:27 package.json
-rwxrwxrwx 1 node node 29324 Sep 8 17:27 package-lock.json
-rwxrwxrwx 1 node node 7867 Sep 8 17:27 README.md
-rwxrwxrwx 1 node node 2757 Sep 8 17:27 SECURITY.md
-rwxrwxrwx 1 node node 635 Sep 8 17:27 server.js
drwxrwxrwx 1 node node 0 Sep 8 17:27 .vscode
I can less a file with no issues from the terminal. If I cat a file, it will show the file contents, but there's always a permission denied line line after the file: cat: server.js: Permission denied
Before submitting
What happened?
When using the microsandbox provider, I'm unable to open a functional workspace with vscode.
What did you expect to happen instead?
The sandbox opens and is functional.
Steps to reproduce
devcontainer.json
Error output / logs
How often does this happen?
Every time
Operating system
Windows
Linux distribution (if applicable)
No response
Architecture
AMD64
Desktop app or CLI?
Desktop app
Devsy version
v1.17.0
Devsy provider
microsandbox
Provider version
v1.0.0
Screenshots
Anything else?
File ownership doesn't seem to be an issue:
I can less a file with no issues from the terminal. If I cat a file, it will show the file contents, but there's always a permission denied line line after the file:
cat: server.js: Permission denied