Docker image tagged versions

[mddeff]

Hey,

First: Amazing project! I was blown away when my buddy showed me this last Friday! Thank you to all the contributors of this project for making something like this accessible to mere mortals.

My question comes as I'm trying to write a Helm chart for this app. I based it off of the production docker compose file. In there, I noticed it's pointing at the docker stable tag, which, based off of the GitHub releases, is version 0.7.4. But hub.docker.com tells a different tale:

While the 0.7.4 tag and the stable tag were pushed at the same time, that seems to be where the similarities end. The hashes are different, and the 0.7.4 tag is almost 50MB larger. It's usually best practice to point at an image tag in the helm chart that doesnt change, so I'm trying to avoid stable. Any insight to the differences? Thanks!

(If I missed something obvious in the repo/docs that explains this, my apologies.)

[SchrodingersGat]

@mddeff thanks for your kind words 👍

You are right that 0.7.4 and stable should be the same image. That is how it is intended. I was not aware that the images were building differently

From looking through the image digests for stable and 0.7.4 it appears they are mostly the same, except for this step:

The docker build behaves differently if it is running from a git tag or a branch. So functionally the images are the same but one contains some more git history.

For now, you can continue under the assumption that stable always points to the latest release.

Please note that for the next major release (0.8.0) we have changed the way that the docker build works, so this particular problem will no longer be an issue

I hope that you enjoy using our software, and thanks for pointing this out.

[matmair]

@mddeff were you successful in creating a helm chart? Might be an interesting deployment method.