Laurent Goderre

The image gets a SHA but it doesn't check the integrity of the package against it. It seems like it didn't check in previous versions either.

@rbioteau my bad, I haven't seen this way of validating before

Not a blocker but typically there is a tag for each variant that default to a specific version (i.e. `ubuntu`, `debian`) so someone can do `docker run azul-zulu:ubuntu`

Since most of the test have the same setup logic, it might be desirable to convert them to use bash functions with parameters for the varying parts

Would it be possible to have an orphan branch that doesn't have all the rest of the code. Cloning even the docker branch is several hundred of meg and takes...

I mean regularly not to slow down the builds

ooh no., if there is a separate repo then we don't need the orphan branch

Not a bocker but would it be possible to use more descriptive variable name and make them `ENV` to help readability. Something like ```Dockerfile ENV JDK_VERSION_LTS=21.0.2 ENV JDK_VERSION_CURRENT=22.0.0 ```

@whalelines I think this is a problem of the tag existing but not being updated anymore (not supported).I do feel like upgrading to a supported version of Go goes beyond...

@tianon it can be but this is mostly to prevent duplicate builds of the same thing