search

metanorma / metanorma-docker

Docker container for running the Metanorma toolchain
https://www.metanorma.com
5 stars 3 forks source link

Publish the latest stable (i.e. tested) image to `latest` tag #163

Closed ronaldtse closed 1 year ago

ronaldtse commented 1 year ago

Right now the latest image pushes go to main, etc, but there is no latest.

e.g.

$ docker image inspect metanorma/metanorma:main
[
    {
        "Id": "sha256:e21454482c4f9cd1cae4d52f2db72205931c8ca104c2c064dba9fbe1e769ad2c",
        "RepoTags": [
            "metanorma/metanorma:main"
        ],
        "RepoDigests": [
            "metanorma/metanorma@sha256:1c3a470ae2933b8dee8c0214568e4159b105aa76498692f10cd88ccac8442bfe"
        ],
        "Parent": "",
        "Comment": "buildkit.dockerfile.v0",
        "Created": "2022-09-09T01:15:00.102621191Z",
...

But:

$ docker image inspect metanorma/metanorma:latest
[
    {
        "Id": "sha256:788cebdd1bb8539827321bd97d51e8dcd29b249578bb85c4a269ec07b179e5e5",
        "RepoTags": [
            "metanorma/metanorma:latest"
        ],
        "RepoDigests": [
            "metanorma/metanorma@sha256:e6dedd50e0be47298deb48a216e44af705cf85f2e8691b0db64edbbf99cd5d52"
        ],
        "Parent": "",
        "Comment": "buildkit.dockerfile.v0",
        "Created": "2022-08-29T15:35:26.093618478Z",
...
ronaldtse commented 1 year ago

From @CAMOBAP :

Because tags decisions made by "docker/metadata-action@v3" I think "latest" wasn't pushed because we used "v1.6.0-pre.1" version -i.e. because of "pre" component

CAMOBAP commented 1 year ago

metanrma-cli@1.6.1 initiated

CAMOBAP commented 1 year ago

Done https://hub.docker.com/layers/metanorma/metanorma/latest/images/sha256-c5084460ea9faa473455602c6aadbcc2fa5f647b732ff0f5b01e97b8e575d715?context=explore