Jason Hall

> Re buildpacks, it looks like it [creates its own Dockerfile](https://github.com/buildpacks/pack/issues/756). Prob fine in most cases but don't think it would work for some of my own own images. (Eg,...

> Anyone tried with version 1.7.0? v1.7.0 is about 4 months old, and had some showstopper auth issues, and :latest currently points to :v1.6.0, so I would guess that not...

> Guess the only solution is waiting for another commit-tagged image or 1.8.0 to be released It sounds like whatever bug is causing that is still present, so it won't...

Just to check, do you get reproducible builds if your builder is `golang:1.17` or even `:1.16`? There were some build stamping changes in 1.18 that may be causing reproducibility to...

> I'm having a hard time running kaniko on openshift with as non root and non privileged. What specific errors are you seeing, and what are you trying to do?

There have been some bugs with `v1.7.0` related to auth, specifically against GCR, that caused us to roll back `:latest` to point at `v1.6.0`. I believe these issues are fixed...

I don't think it should be necessary* -- in v1.6.0 and v1.7.0 it was initialized in the Dockerfile (setting up `/kaniko/.config/gcloud/docker_credential_gcr_config.json` which the helper uses), and at head the cred...

Well that's a little surprising to me. 🤔 It works with a step to initialize the cred helper? What's that look like? And this is with the kaniko executor @main?...

> I thought dockerhub had the issue but apparently, I had authentication issues with :latest tag, I didn't realize that you rollback to 1.6 so I thought dockerhub had the...

@BarthV could you do me a favor, and try this build without your `~/.docker/config.json` file mounted in? There were changes since v1.7.0 to compile in the cred helper logic into...