-
Notifications
You must be signed in to change notification settings - Fork 65
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
Error 'container not running' on 'writing container filesystem' step #1213
Comments
@tkrishtop Is this for |
Hi @acornett21 thank you for checking.
yes, here is preflight.log
The error code 143 suggests that the podman process was terminated by a SIGTERM (signal 15).
When we test having images pre-pulled locally, the error disappears. That makes me think that we really deal with preflight killing podman pull here and not with the resource constraints.
Do you use any workarounds to fix the issue? |
For clarity, preflight doesn't use podman, so there is not Since this works with cached images, I'm going to make the logical assumption that this is the same problem as konflux with resources on the host. Can you check the CPU/Memory profile on the host to see if DCI is killing this? For Konflux, users can increase the CPU/Memory of their pipeline or task. I'd assume DCI has a similar feature. |
I also just tested the below image a few times which is almost 8GB and preflight has no issue (assuming you have enough
I tested this directly on a host with the preflight binary. So no container, CI, etc concerns. This makes me think it's more of a CI issue, since this is double the size of the largest image in question. |
Bug Description
One of Arkady's Telco partners has particularly large images, 2-4GB. They statistically frequently have an error 'container not running'. It seems to be related to the fact that preflight tries to run a container before having it fully-pulled.
Version and Command Invocation
1.10.0
Steps to Reproduce:
Expected Result
preflight running normally 100% of time instead of random occurrences of 'container not running'
Actual Result
random occurrences of 'container not running'
Additional Context
The code source producing an error seems to be here. Should we explore the crane options to ensure that the image was completely pulled and include them into preflight code?
The text was updated successfully, but these errors were encountered: