Sebastian Davids

One uses `SOURCE_DATE_EPOCH` as follows: ```console $ SOURCE_DATE_EPOCH=0 docker buildx bake $ SOURCE_DATE_EPOCH=42 docker buildx bake ``` Does this PR support this use case? `SOURCE_DATE_EPOCH` is used to pass a...

Maybe I was not clear enough in #3197: ```console $ SOURCE_DATE_EPOCH=0 docker buildx bake ``` ```hcl labels = { "org.opencontainers.image.created" = "how do I get SOURCE_DATE_EPOCH as an RFC3339-formatted string...

It could be: If `$HOME` is set then set `user.home="$(realpath $HOME)"` Or: Run java once and check whether `System.getProperty("user.home")` returns `?` in that case use `$HOME` or if not set...

As I wrote above ```console $ docker run --rm -u "$(id -u):$(id -g)" -it -e HOME=/tmp asciidoctor/docker-asciidoctor:1.89.0 bash -c "java -XshowSettings:properties -version 2>&1 >/dev/null | grep 'user.home'" user.home = ?...

As you can see, I am using the official `asciidoctor/docker-asciidoctor` image – so the official image would have to upgrade to JDK 21.

I have opened https://github.com/asciidoctor/docker-asciidoctor/issues/525.

Having the workaround in this Gem also, might not hurt either …

I investigated a little with [dive](https://github.com/wagoodman/dive): https://github.com/asciidoctor/docker-asciidoctor/blob/8b9e96bc6caa495da00f0c7b5817e4554c7c8faa/Dockerfile#L62-L92 The command above creates the symlinks. ```console $ docker run --rm -it alpine:3.22.0 sh -c 'ls /usr/bin/jshell ; apk add -q --no-progress openjdk21-jre...

I have opened https://gitlab.alpinelinux.org/alpine/aports/-/issues/17318 upstream but I think this PR should be merged regardless.

Having un-targeted symlinks lying around is a CVE waiting to happen … They are easily accessible on top: ```console $ docker run --rm -it asciidoctorw/docker-asciidoctor:1.89 jshell ``` 💥