Cannot Open Docker Workspace on Windows 10

tiibun / vscode-docker-ws

Docker WorkSpace for VSCode

Other

14 stars 2 forks source link

Cannot Open Docker Workspace on Windows 10 #6

Open midacts opened 5 years ago

midacts commented 5 years ago

Docker WS Version: 0.4.1 VS Code Version: 1.36.1 Windows 10 version: 10.0.15063.0

Docker workspaces are not opening up in vscode now.

I've tried on my work and home machines and it happens in both locations. Maybe something has changed in the latest version of vscode.

tiibun commented 5 years ago

@Midacts I confirmed. I will investigate, but I think it is better to use this: https://code.visualstudio.com/docs/remote/containers

midacts commented 5 years ago

Thanks for the reply. I found the extension yesterday and was able to use it.

Sorry : / Thanks for all your work on this project.

On Wed, Jul 24, 2019, 10:34 PM tiibun notifications@github.com wrote:

@Midacts https://github.com/Midacts I confirmed. I will investigate, but I think it is better to use this: https://code.visualstudio.com/docs/remote/containers

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tiibun/vscode-docker-ws/issues/6?email_source=notifications&email_token=AA6G3EFZQ2NFSU5UCODJUILQBEGJXA5CNFSM4IGHAWUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2YE6EY#issuecomment-514871059, or mute the thread https://github.com/notifications/unsubscribe-auth/AA6G3EG3UBORYMELOWUE6K3QBEGJXANCNFSM4IGHAWUA .

guiurocafortferrer commented 4 years ago

Any news on this issue ?

I am experimenting the same issues with Windows 10, with the following versions:

Version: 1.43.1 (user setup) Commit: fe22a9645b44368865c0ba92e2fb881ff1afce94 Date: 2020-03-18T07:01:20.184Z Electron: 7.1.11 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Windows_NT x64 10.0.18362

Vscode Workspace 0.4.1

I checked the Docker Workspace extension output, but could not find anything at all. Any idea about how i could obtain some more debugging information to try pinpoint the problem ?