Container Image Tags are not working as listed in the README

[peterge-misoft]

Hey, I am just facing a problem with the version scheme of the container image tags. I am not completely sure if I am just misunderstanding sth or if there is a problem with netbox-docker.

The Readme writes this:

We recommend to use either the vX.Y.Z-a.b.c tags or the vX.Y-a.b.c tags in production!

So I use these lines in my docker-compose.override.yml:

  netbox:
    image: docker.io/netboxcommunity/netbox:${VERSION-v3.7-2.8.0}
  netbox-housekeeping:
    image: docker.io/netboxcommunity/netbox:${VERSION-v3.7-2.8.0}
  netbox-worker:
    image: docker.io/netboxcommunity/netbox:${VERSION-v3.7-2.8.0}

I understand this, to alway use the latest 3.7.X version of netbox with netbox-docker 2.8.0.

1. Tonight 3.7.5 came out, and after I executed docker compose pull & docker compose up -d, the version was still on 3.7.4.
2. So i switched all 3 lines to ${VERSION-latest-2.8.0}, executed docker compose pull & docker compose up -d and my instance was on 3.7.5.
3. But after I changed those 3 lines back to ${VERSION-v3.7-2.8.0} and executed docker compose pull & docker compose up -d, my instance was back on 3.7.4.

Why?
If I see it correctly, the vX.Y-a.b.c version tags are not working correctly. Am I overseeing sth?

[cimnine]

From the README:

New container images are built and published automatically every ~24h.

Could it be that you were just too eager to get the latest & greatest?

[peterge-misoft]

Yep, today after our nighly auto-update-ci run, netbox got updated to 3.7.6 which was released yesterday.

I just did not notice this line applies to all versioned images, I thought building every ~24h just applies for the feature/beta tags, so yeah i was too eager all in all 😬