-
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
Prebuild process gets stuck (when updating .gitpod.Dockerfile
)
#4856
Comments
Update 1:One of the workspaces (https://gitpod.io/start/#black-ferret-dd1kh8y8) that seemed to be stuck on "Build an image" screen and empty output, finally has some (error output).
|
Update 3:After a few hours, it was no longer stuck. |
https://gitpod.io/#https://github.com/ghuntley/learn-graphql/tree/gh/gitpodify Confirming that I've also witnessed the following as of moments ago
|
Outch... this feels like a restart-cycle because we miss some signal. Might have been introduced with the recent headless-log changes. 😕 Will dig into this shortly. |
Thx so much @shaal for this treasure trove of data. It's a bit entangled, bit it seems like here are multiple strange things (bugs?) happening here:
Will try to verify and fix one-by-one. |
Thank you for the quick response, let me know if I can help testing. |
Ok, pinned it down:
Besides the first error which we're going to fix in #4875 there are two issues left:
|
@geropl Do you know why image build takes so long? At least in my case,
|
Hm, not sure. Maybe my hypothesis (long build) is wrong, but it was the only way I could reproduce the error case. It could be that there is another error within |
I updated the It still looks like the prebuild is stuck. I am assuming that's expected, because the fix will be done through the follow-up issues? |
@shaal I tried the context you linked above (https://github.com/shaal/DrupalPod/blob/debug-with-tmate/.gitpod/.gitpod.Dockerfile) and it hung for me as well, but during image build, not prebuild. And it did so in this It feels this is unrelated to the original problem in this issue (which started multiple workspaces on broken image builds) which got fixed in the meantime, so I opt for closing this. Especially as I see you opened #4936 which looks like a follow up. D'accord? |
Bug description
When updating
![image](https://user-images.githubusercontent.com/22901/126050495-38c3f390-c289-44a6-a970-8d1a6c4f0b7f.png)
.gitpod.Dockerfile
and pushing it back to repo on a branch, the prebuild seems stuck.It takes over half an hour (but I am not sure how long, perhaps 1 hour?) where all I see is this screen with jumping G.
(while console doesn't display any error)
Coming back to the computer after a while, I see this screen -
![image](https://user-images.githubusercontent.com/22901/126050511-ee421691-f789-4b2c-be3e-83bbd4f03be6.png)
And here's the output I found in
console
-https://gist.github.com/shaal/b34b1e2ffba2d50deb4e42a3b4ed961c
I checked
gitpod.io/workspaces
, and I see 5(?) workspaces running, even that I only opened 2 windows of the following URL, expecting to see the prebuild output - https://gitpod.io/#https://github.com/shaal/DrupalPod/tree/debug-with-tmateSteps to reproduce
In my experience, it is difficult to replicate or anticipate how prebuild behave (especially with custom docker image build)
This happened to me also the other day, when I worked on https://github.com/phase2/outline/tree/gitpod, when I opened an issue in https://community.gitpod.io/t/prebuild-is-stuck/4171
I think I usually use the manual prebuild using the
#prebuild/
in the URL, but in repos that has the Gitpod bot, I would get a message that a prebuild is already running.These workspaces supposed to run prebuild, but they are stuck, and once 4 workspaces are "running", I cannot open another one, but at the same time I cannot stop a prebuild that is stuck like that.
So, I usually wait a few hours, then the workspaces are shutdown, and I can run prebuild using the
#prebuild/
in the URL, and then it finally works.Expected behavior
No response
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: