Docker image tag chaos for rtl_433 #58
-
Hi, can anybody please advise me what the the literally dozens of different docker image tags mean? For example what is the difference between hertzg/rtl_433:alpine3-21.05 and hertzg/rtl_433:alpine-3-21.05? And this is just one of probably 100 examples you can find. The tag naming here is an absolute nightmare and I am totally lost what the latest alpine-3 version is. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hello, Sure, It might be overwhelming for some people to see so many tags, I'd be happy to review prs with improved docs regarding the tags. The full format for any version is:
The first
Code snippet responsible for tagging each Alpine based build: rtl_433_docker/images/alpine/config.js Lines 26 to 36 in 36a056d Hope this helps :) |
Beta Was this translation helpful? Give feedback.
Hello,
Sure, It might be overwhelming for some people to see so many tags, I'd be happy to review prs with improved docs regarding the tags.
I'll try to explain better here.
The full format for any version is:
hertzg/rtl_433:<flavour>-<flavour_version>-<rtl433_version>
There are aliases for alpine, for example container which is based on
alpine 3.15.0
(currently targeted latest version) would end generating 3 more tags for the same container (same hash).hertzg/rtl_433:alpine-3.15.0-<rtl433_version>
hertzg/rtl_433:alpine-3.15-<rtl433_version>
hertzg/rtl_433:alpine-3-<rtl433_version>
The first
-
after the flavour name is optional for alpine and can be ommited which means the same image g…