Tangled releases tagged releases of the knot software, the latest being v1.20.0
Would it makes sense for the Dockerfile to target a tagged release instead?
- arg TAG='master'
+ arg TAG='v1.20.0'
It would make sense as then the knot-docker repo can then also have tagged releases of the Dockerfile too which align with the versioning of the upstream core. This should reduce confusion for those updating their knots, also could lead for automated tagged builds of knot-docker to be pushed to atcr.io (or other distribution platforms).
yeah that's a good idea lol. was tossing that up today but too busy to do properly. should be a couple of lines whoever gets to it first