Kaniko should abort if pkg/filesystem/resolve.go ResolvePaths() founds symlink target doesn't exist #2709
Labels
area/errorhandling
For all bugs having to do with handling problems during kaniko execution
area/symlinks
kind/enhancement
New feature or request
kind/friction
needs-discussion
Items which need more discussion before commitment
priority/p1
Basic need feature compatibility with docker build. we should be working on this next.
Actual behavior
Kaniko is being used by Debian's Salsa CI (a CI toolkit in the Debian's gitlab instance). Debian is also in the process to being /usr-merged. A recent upload of the
debianutils
package introduced a related bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050784Due to that bug, the images built by kaniko were broken, and pushed to the salsa ci registry. All the Salsa CI (package build) jobs
were unable to run.
Expected behavior
It would had really help if kaniko exited with error when it found this error:
https://salsa.debian.org/salsa-ci-team/pipeline/-/jobs/4620766#L291
So a still working image could be used by all the Debian Salsa CI users.
To Reproduce
Steps to reproduce the behavior:
Additional Information
Given the debian build system and mirrors, it is not possible right now to provide a Dockerfile that install debianutils 5.10. I will do once it gets fetched by snapshot.debian.org.
Triage Notes for the Maintainers
--cache
flag-
See See salsa.debian.org/salsa-ci-team/pipeline/-/commit/7788516dd8b2a3fd82f7cb62064bae5a2ba79a3bThe text was updated successfully, but these errors were encountered: