-
Notifications
You must be signed in to change notification settings - Fork 322
Crash building trivial config #6851
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
Comments
I've got the same issue. At first glance, it appears to be an issue with permission, but it seems outside of our control. A quick fix for now is removing the "features" section from the devcontainer.json. I'm guessing somebody is already working on it to fix it |
Could you append the full log containing the error? |
It appears to work correctly after a few hours of reporting the bug, and I can't reproduce it right now. As far as I can remember, it seems to be related to when we tried to pull some docker image that would build the git feature. The docker image seemed to have been restricted for a few hours, which would fail the git feature part of the devcontainer.json (I'm guessing other features too, but I did not test it at the time). |
Thanks, let us know when this occurs again. I'll look into improving the log message. |
In fact, it appers to be related to this issue #6819 Downgrading to the older version (0.234.0) fixes the issue, but I'm still not sure why... |
Could you append the full log containing the error? |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Just upgraded VScode and the remote-containers extension to latest. Full log:
|
Apparently this is caused by the generated Dockerfile not being on the same drive as the context. Continuing in devcontainers/cli#240. |
Steps to Reproduce:
Dockerfile:
devcontainer.json:
This is worrying because:
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: If I disable all extensions I won't get the remote containers extension so how I am supposed to check this?
WSL and Docker work fine on this machine, I use this regularly for other things.
BTW I don't know if this is the right repo to report this, apologies if that's not the case.
Many thanks
The text was updated successfully, but these errors were encountered: