-
Notifications
You must be signed in to change notification settings - Fork 1.3k
github.com/microsoft/vscode cannot be launched with Building Image #9499
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'm wondering if this is due to https://github.com/gitpod-io/definitely-gp/tree/master/vscode |
Thanks for pointing out, but I do no think so. https://github.com/gitpod-io/definitely-gp/blob/d0832d385a65b0d990145184e6a36491d9cf0554/vscode/Dockerfile is based on focal, so we can run the following commands on Docker 20.10.14:
The error (even in |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
As of today, the issue does not look resolved:
|
It's indeed #8473.
@tnir Your test works because you put a "sudo" in front. If you don't you receive said failure. A workaround would be to fix the Dockerfile in definitely-gp by adding a |
Bug description
https://gitpod.io/#github.com/microsoft/vscode (HEAD = ed06c9f3cf1fdbabd692df48d8c0dfd993b17434 as of writing) cannot be launched with "Building Image", but "Continue with Default Image" does work.
Error log in
Building Image
Full log
Steps to reproduce
Workspace affected
No response
Expected behavior
apt-get update
command (or writing on/var/lib/apt/lists
) should work.Example repository
https://github.com/microsoft/vscode/tree/ed06c9f3cf1fdbabd692df48d8c0dfd993b17434
Anything else?
No response
The text was updated successfully, but these errors were encountered: