Copilot stopped working in devcontainer suddenly #36728
Replies: 4 comments 6 replies
-
|
@perezd Thank you for your feedback, Our copilot team is investigating this |
Beta Was this translation helpful? Give feedback.
-
|
Hey there @perezd and thank you for asking a good question! I'm glad you found our community 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Hello. There is no error mesage in log. I can see extension is succesfully instaled in container, but in runtime status window of extension i see: "Not yet activated". Versions of VSCode and Github Copilot extensions are up to date. You can simulate it in this simple devcontainer: Some outputs of running container you can see here: Thanks for any advice. Github Copilot is awesome assistant and after some testing a like to recommend it at work like official tool for developers. |
Beta Was this translation helpful? Give feedback.
-
|
I try it next day and surprise-surprise...still not working. But i found "hotfix". It is possible force extension not to run from container, but from UI part of vscode. Add this lines to settings.json: |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Copilot was recently updated to: v1.54.7077
I just recently updated VSCode to:
Prior to this, I had a working Copilot instance running from within a devcontainer, and suddenly it just stopped working...I don't see anything strange in the output log either, just this:
If I pop out of the devcontainer into a local VSCode Copilot works as I expect...so something must have gone wrong recently. I've also obliterated the container image, signed in/out of things, and all the standard checks.
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions