Open abhi1git opened 4 years ago
It seems that GitLab Kubernetes Runner pods may appear stuck when the build
container is OOMKilled, as the helper
container keeps running in that case until job timeout. In our case this is exactly what is happening.
So the issue for us is not about performance at all, but rather about memory usage.
Actual behavior While building image using gcr.io/kaniko-project/executor:debug in gitlab CI runner hosted on kubernetes using helm chart the image build process freezes on Taking snapshot of full filesystem... for the time till the runner timeouts(1 hr) This behaviour is intermittent as for the same project image build stage works sometimes
Issue arises in multistage as well as single stage Dockerfile.
Expected behavior Image build should not freeze at
Taking snapshot of full filesystem...
and should be successful everytime.To Reproduce As the behaviour is intermittent not sure how it can be reproduced
--cache
flag@tejal29