-
Notifications
You must be signed in to change notification settings - Fork 103
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
Server crashes when trying to restart pending build #503
Comments
hi @espenaf I opened pull request which fixes pulling docker images from third party registries such of a grc.io but in my case does not fix your issue. I investigated a bit more into this and seems like |
Ahh. Did not know the standard jib container build images did not have a shell. Switched to using docker.io/adoptopenjdk/maven-openjdk11 now, but still the same issue, but maybe your #503 also fixes pulls from docker.io? |
try to use just |
PR will be merged later after review from someone. |
Getting the same error:
The build status is now stuck in "running" with no value in the output, and i can`t stop or restart the build. If i do a restart it crashes with the error above. Stop has no effect. |
thanks for reporting this, I'll try to reproduce that and make a fix. btw build status is stuck because server is down after this. |
If i restart the server the build will still be stuck in running state. Trying to stop it then will have no effect in the UI, while the server logs a call to /api/v1/builds/stop with return code=200, and if then try to restart, the server crashes again. |
Running server and worker on CentOS 8 via podman. While trying to restart a build which is stuck in pending state the following error is thrown in the server, and the container crashes:
The build config is added manually via the UI, and has the following setting
The text was updated successfully, but these errors were encountered: