tspearconquest

Hello, I'd like to ask for a documentation update. The below code: ``` #!/bin/busybox sh set -o pipefail ``` Results in: ``` In script.sh line 3: set -o pipefail ^------^...

Hi! I don't disagree with anything you said, and I hope that can clarify that my ask was just simply to list out in the documentation that there are other...

> This makes the image unusable in some circumstances due to the wrong permissions on /tmp. I believe #2192 may be responsible (or contributing anyway) to the issue.

Interestingly, The below dockerfile seems to get past the issue, but it has other issues: ``` FROM scratch as one RUN --mount=from=docker.io/busybox:musl,dst=/usr/ ["/busybox/busybox", "sh", "-c", "/busybox/mkdir -p /kaniko && /busybox/chmod...

I also tested out if I could make any progress using the `--use-new-run` flag but the results were the same.

Another thing I noticed when I made some additional heavy modifications to the `Dockerfile_debug` file that make the image build but result in a different filesystem layout, when I do...

Another example: Dockerfile ``` FROM scratch as one RUN --mount=from=docker.io/busybox:musl,dst=/usr/ ["/busybox/busybox", "sh", "-c", "/busybox/find / >/output"] FROM busybox:musl as two COPY --from=one /output / CMD cat /output ``` Kaniko executor...

Hey, thanks for making this. I apologize as I haven't had proper time to work on this after all. This looks good to me, however I'm not a maintainer so...

This would be useful in checking any kind of text files are encoded in the desired user-configurable encoding. Regardless of whether it treats or mitigates the CVE, this has value...

Any progress on this?