-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extensions are not installed when configured in devcontainer.json #5665
Comments
Can you please share the remote server logs? |
yes. logs are attached |
Attached logs does not contain remote server logs and they include all sessions logs. Can you please provide the log of the remote window?
|
I can only test it once a week and today it works using eduroam wifi. Is it possible to see the "Remote Server" Logs from last week? Is it a file which is stored somewhere? |
Sorry - I don't understand. What do you mean by "server bits"? |
I got it now. Using the terminal i figured out the location of the logs. Unfortunately, there is only one folder with logs from today (although it's the folder/devcontainer which did not work in eduroam wifi) |
Please provide the remote server logs if you are able to reproduce it again. |
I tried on three different days, problem didn't come back. I'll close the ticket and open it again, when it happens again. |
Same behaviour as described here #5620 but in my case there are no certificate errors in the log.
When I try to open a remote container it looks like it works except for activating all the extensions defined in devcontainer.json. It happens for me and some of my students using Windows 10 when connected to eduroam Wifi. The problem only appears for some Windows 10 Laptops, not every Windows 10 Laptop is affected. We didn't notice those problems with Ubuntu Laptops.
In my Wifi at home, with the same laptop which was connected to eduroam before, after rebuilding the container it works as expected: all the extensions defined in devcontainer.json are installed.
So it maybe has something to do with eduroam (enterprise wifi?).
Any ideas what we could do? We can't see any helpful error messages in the logs.
The text was updated successfully, but these errors were encountered: