-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Gitlab CI failed due to Taking snapshot of the full system for more than 1 hour #1516
Comments
Sorry about the flakiness. |
In the /kaniko/executor line, you don't have a space before the "--dockerfile" line. I'd be surprised if that gave this error, that'd stop it from getting the right context/loading the docker file. Just in case though :) |
Same erreur using Kaniko with Gitlab CI and the following command: /kaniko/executor \
--cache=true \
--cache-ttl=168h \
--context $CI_PROJECT_DIR \
--build-arg GIT_COMMIT_SHORT_SHA=$CI_COMMIT_SHORT_SHA \
--build-arg REPO_AUTH_JSON=$repo_auth_json \
--dockerfile $CI_PROJECT_DIR/docker-k8s/Dockerfile \
--destination $CI_REGISTRY_IMAGE:$CI_COMMIT_SHORT_SHA Tried with image |
It seems that removing |
It works for me when removing |
Same issue here with 1.9.0-debug and 1.9.1-debug - but i even don't have any "--cache*" params, but still does not work |
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
The text was updated successfully, but these errors were encountered: