BUG: Gitpod Instance build failing at startup
See original GitHub issueDescribe the issue:
The gitpod instance build is failing at startup due to cython
version being 0.29.28
and required is Cython >= 0.29.30.
I suspect it is due to the recent change made in environment.yml
(maybe other changes as well, but I was only able to find this one involving cython)
Reproduce the code example:
Open Gitpod Instance via Numpy repo
Error message:
No response
NumPy/Python version information:
No version output, As numpy isn’t building.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Failing to build Image · Issue #10303 · gitpod-io ... - GitHub
Bug description When I try to create a new workspace for my repository, the page get stuck in "Building Image" and the log...
Read more >Troubleshooting - Gitpod
What can I do if I have unsynced data inside a workspace but it's not starting? · Go to the Gitpod Dashboard ·...
Read more >Gitpod integration - GitLab Docs
Go to your merge request. In the upper right corner, select Code, then select Open in Gitpod. Gitpod builds your development environment for...
Read more >Error: Failed to launch the browser process puppeteer
I had the same issue, I tried everything which is listed from the Puppeteer guide, none of them worked for me.
Read more >I used Gitpod to start a new project - here's how I found it
Your normal VS Code extensions can be added to the workspace on startup by adding them to the .gitpod.yml file. For instance
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Okay, new image now built successfully. (log) for future reference.
If an
environment.yml
is updated I have observed(Not a fact, but just an observation), in about 24 Hours the latest image gets pushed to dockerHub, which gitpod uses as a base