-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Cannot pull a newly regenerated image after the latest changes to Gitpod #3838
Comments
Uhm, today I've tried again with VSCode UI and I managed to pull the image. Don't know what happened in the meanwhile. |
I am not sure that it is related to Theia or VS Code. Image pulling happens before IDE is running. cc @csweichel |
This issue is indeed unrelated to VS Code. It would seem that there was some configuration change/something broke on the image builder. |
This makes more sense indeed and also explains why I'm now able to pull the image smoothly in VS Code as well. |
@pattacini, was this a temporary issue? it seems to work now, or do I miss anything here? |
Yep, perfectly working now! |
Bug description
I’m unable to pull a newly regenerated image as per the screenshot provided below.
This happens only when I select VS Code as the preferred UI.
With Theia, everything works as expected.
Steps to reproduce
Just run Gitpod on the example repository I've provided down here.
Expected behavior
The docker image should be pulled correctly.
Example repository
https://github.com/robotology/icub-gazebo-grasping-sandbox
The text was updated successfully, but these errors were encountered: