Open dlaidlaw opened 3 years ago
Same here :/
This only happens if you copy / to / - Seems to be looping somewhere and constantly eating up disk...
Yes, it seems to be having a problem copying the /dev directory from the source image. Still a bug, I think. Anyone have a workaround they use?
Possible dupe of https://github.com/GoogleContainerTools/kaniko/issues/1596
Actual behavior Executing a multi stage build works with the docker command, but hangs using kaniko. The kaniko command runs for a very long time (more than 30 minutes). The last log output from kaniko is
INFO[0058] Saving file . for later use
The same failure is observed running the kaniko build in either a gitlab-runner or from the Mac OSX command line. When run in the gitlab-runner (running in kubernetes) the build runs for about 8.5 minutes with an error message of
ERROR: Job failed: command terminated with exit code 137
Expected behavior Kaniko should build the image. It should not take more than about 2 minutes. Building with the docker command using the same context and Dockerfile works OK, and takes between 15 and 30 seconds to run.
To Reproduce Steps to reproduce the behavior:
Additional Information
Kaniko Image (fully qualified with digest)
Log output from kaniko
Triage Notes for the Maintainers
--cache
flag