Mosquitto v2.0.15 instead of latest or v2.0.18

Hi everyone,

I just noticed that the Mosquitto version is v2.0.15 and not latest like most containers created by Gladys.

Mosquitto is currently at version 2.0.18 and that fixes several (8) vulnerabilities.

V2.0.15

v2.0.18

Is there a reason for that?
(Personally, I like to see container versions and be able to act on them, because sometimes updates are not completed, e.g. Z2MQTT which loses some devices)

Thanks in advance

Here is a PR, but since I haven’t set up the dev features I didn’t test it. The only change is the mqtt version; no code changes

I haven’t looked, but it would be good practice not to use « latest » on Docker images.

If we update blindly, it might stop working one day because of an upgrade of another container which can also mess up the system if there are « breaking changes ».

In my opinion we should therefore open a ticket each time associated with the Docker

Currently, apart from Mosquitto (on my instance with only Zigbee2MQTT and Mosquitto) only Mosquitto is using a numbered version; the rest are on « latest ». I think it’s because of Watchtower but I’ll confirm that pinning the version might be the best thing to do.

There was a bug in version 16, so we pinned the image to version 15

2 Likes

But it’s worth testing 2.0.18, yes, thanks for your PR

2 Likes

Yes, I made a PR a bit hastily, sorry. I’ll be more careful next time.