Dockerised Zabbix 7.4.3 to 7.4.5 Causes Docker Scrim failured
Hi.
Quick heads up for others: we've have a dockerised Zabbix build using the formal docker compose files from github for learning on.
It was using zabbix alpine mysql originally built using the 7.4.3 images and docker files.
We upgraded to 7.4.5 today with a docker compose pull, docker compose down, down compose rm, docker compose up, and the server container failed with a docker Scrim error.
Having a dig around, including failing to reload using the 7.4.3 images, we couldn't get it to work so we pulled the latest docker compose files, and docker compose up from that: that worked and no scrim error was created.
As far as I'm aware, we've not had a minor zabbix version NEED a docker compose file uplift before, so this was a first, but I'm not sure how often the alpine OS image rolls in a minor release.
We are also investigating why we lost our full database with this upgrade :we could have inadvertently deleted a persistent volume in the process of trying to fix the problem, or the path of the mysql database volume has changed and we've missed it.
We're currently going through the change logs for the docker files and 7.4.4 and 7.4.5 to see if we can pinpoint the cause, but for the moment, if you are in a similar boat, pull the latest docker compose files and run with that.
If anyone else has this issue, please let me know it's not just me!
Quick heads up for others: we've have a dockerised Zabbix build using the formal docker compose files from github for learning on.
It was using zabbix alpine mysql originally built using the 7.4.3 images and docker files.
We upgraded to 7.4.5 today with a docker compose pull, docker compose down, down compose rm, docker compose up, and the server container failed with a docker Scrim error.
Having a dig around, including failing to reload using the 7.4.3 images, we couldn't get it to work so we pulled the latest docker compose files, and docker compose up from that: that worked and no scrim error was created.
As far as I'm aware, we've not had a minor zabbix version NEED a docker compose file uplift before, so this was a first, but I'm not sure how often the alpine OS image rolls in a minor release.
We are also investigating why we lost our full database with this upgrade :we could have inadvertently deleted a persistent volume in the process of trying to fix the problem, or the path of the mysql database volume has changed and we've missed it.
We're currently going through the change logs for the docker files and 7.4.4 and 7.4.5 to see if we can pinpoint the cause, but for the moment, if you are in a similar boat, pull the latest docker compose files and run with that.
If anyone else has this issue, please let me know it's not just me!