Open gabegorelick opened 2 years ago
Hi @gabegorelick,
Thank you for pointing out this bug, I agree that the duplicate preresolved origin should probably not be there and could cause confusion. Additionally, in CI we want the same inputs to create the same outputs. For those reasons we agree that kbld should not append duplicate preresolved entries in the origins.
Hi @gabegorelick
We have merged this PR into develop. Assuming all goes well, expect to see this bug fix in the next kbld release!
Should this issue be closed? The MR has been merged well over a year ago.
What steps did you take:
kbld -f foo.yaml --imgpkg-lock-output lock.yaml
kbld -f foo.yaml -f lock.yaml --imgpkg-lock-output lock.yaml
preresolved
entry underkbld.carvel.dev/origins
. So far so good.kbld -f foo.yaml -f lock.yaml --imgpkg-lock-output lock.yaml
preresolved
What happened: In general, every time you run kbld while passing in the lockfile, kbld will append another
preresolved
entry.Example:
What did you expect: Stop after the first addition of
preresolved
.Anything else you would like to add: https://kubernetes.slack.com/archives/CH8KCCKA5/p1640125213244500?thread_ts=1640041938.237600&cid=CH8KCCKA5
Environment:
kbld --version
): 0.32.0Docker HUB
): n/a/etc/os-release
): macOSIf building images using
docker
: n/adocker version
)If building images using
buildkit
: n/akubectl buildkit version
):kubectl version
):If building images using
pack
pack version
):Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible" 👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.