Currently, the deephaven images have a set of basic details about how the image building process is parameterized:
$ docker inspect --format '{{ json .Config.Labels }}' ghcr.io/deephaven/server:latest | jq
{
"io.deephaven.image.type": "server",
"io.deephaven.server.grpc-health-probe.version": "0.4.15",
"io.deephaven.server.java.base.name": "docker.io/eclipse-temurin:17",
"io.deephaven.server.java.version": "17",
"io.deephaven.server.python.requirements.type": "server",
"io.deephaven.server.python.version": "3.10",
"io.deephaven.server.sources": "released",
"io.deephaven.server.ubuntu.version": "22.04",
"io.deephaven.server.version": "0.23.0",
"org.opencontainers.image.authors": "developers@deephaven.io",
"org.opencontainers.image.base.name": "docker.io/ubuntu:22.04",
"org.opencontainers.image.description": "Deephaven Server",
"org.opencontainers.image.licenses": "Deephaven Community License Agreement 1.0",
"org.opencontainers.image.ref.name": "ubuntu",
"org.opencontainers.image.source": "https://github.com/deephaven/deephaven-server-docker",
"org.opencontainers.image.title": "Deephaven Server",
"org.opencontainers.image.url": "https://github.com/deephaven/deephaven-server-docker",
"org.opencontainers.image.vendor": "Deephaven Data Labs",
"org.opencontainers.image.version": "0.23.0"
}
It would not be unreasonable to extract information from the application itself and expose it as labels. For example, the application git commit sha and build date. This is dependent upon deephaven/deephaven-core#3705.
Currently, the deephaven images have a set of basic details about how the image building process is parameterized:
It would not be unreasonable to extract information from the application itself and expose it as labels. For example, the application git commit sha and build date. This is dependent upon deephaven/deephaven-core#3705.