test: fix test breakage caused by external dependency update #3049
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently kaniko CI/CD tests started failing due to external dependency change. Tests are failing stating the ENV produced by kaniko differes from docker now although this failure occured not directly related to a kaniko PR and no kaniko logic related to this has changed recently. PR here attempts to fix this
log snippet
full logs showing the test failure
https://github.com/GoogleContainerTools/kaniko/actions/runs/8177044948/job/22357785283
This test failure is not directly related to any kaniko PR but some external dependency change, either an external image our tests rely (
busybox:latest
) on changing or the docker on the Github Action Runner being updated in some formBy default kaniko adds the following to SCRATCH containers which I believe mirrors how docker works:
This is the env shown when I run
busybox:latest
locally:The fix is to add these ENV vars explicity in the two docker tests seeing issues for now as I believe this is not an issue with kaniko's logic IIUC