So I rewrote the Dockerfile to always fetch the latest release with this:
RUN URL=$(wget -qO- https://api.github.com/repos/comixed/comixed/releases | grep -m 1 "browser_download_url.*\.zip" | cut -d '"' -f 4) \
    && wget -q -O comixed-release.zip "$URL" \
    && unzip comixed-release.zip -d /app \
    && rm comixed-release.zip
But the Dockerfile at present fetches something called -SNAPSHOT and I'm not sure where that was supposed to come from? I think maybe it was a build artifact that was manually attached?

If my solution is good enough I'll make a PR with it.

We use Maven versioning to differentiate unreleased code from released code; i.e., -SNAPSHOT is the "version" of code that's not been released yet. When we create a release, the version in all files across the project are updated and that is replaced with the new release version, including the Dockerfile. We also tag that commit and push that tag into the Github.

The Dockerfile itself is only ever used when we've both set a release version and pushed that tag. That ensures that the Dockerfile pulls the correct version of the release when you pull it.

I hope that explains a bit why we use -SNAPSHOT on the main branch and when the Dockerfile executes.

Uh oh!

Publishing to docker fails #2559

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions