How to upgrade Docker images from 6.4 to 6.4.14? Ubuntu 20.04 LTS

[t7MevELx0]

I have an Ubuntu 20.04 LTS VM running Docker container versions of Zabbix 6.4.1.

When I run `git pull`, it complains about commit changes. To resolve this, I run `git stash` since I'm not managing the repository and I'm unsure why it's complaining. After stashing, I run `git pull` again and see a list of versions, including 6.4.14.

If I run `git checkout 6.4` followed by `docker-compose -f ./docker-compose_v3_alpine_mysql_latest.yaml up -d`, it rebuilds the images, but the Zabbix Web GUI still shows version 6.4.1.

I'm following the procedures listed in the [Zabbix documentation guide](https://www.zabbix.com/documentation...ade/containers).

I noticed that the Zabbix Docker images were installed using the Alpine compose file instead of the Ubuntu compose file. Could this be causing an issue?

Here are the outputs of the Docker inspect commands:

```bash
docker inspect -f '{{ .Config.Image }}' zabbix-docker-zabbix-server-1
# Output: zabbix/zabbix-server-mysql:alpine-6.4-latest

docker inspect -f '{{ .Config.Image }}' zabbix-docker-zabbix-web-nginx-mysql-1
# Output: zabbix/zabbix-web-nginx-mysql:alpine-6.4-latest

docker inspect -f '{{ .Config.Image }}' zabbix-docker-mysql-server-1
# Output: mysql:8.0-oracle
```

Does the `-latest` tag not include the latest build of 6.4?

Managing this software inside a Docker image seems challenging. I feel like `apt-get` would manage this package and its dependencies better. Just running `apt-get update` and `apt-get upgrade` to patch Ubuntu and its packages seems to break this Zabbix Docker install.

Are most of you not using Docker images?

[t7MevELx0]

Is there better documentation on upgrading Zabbix Docker containers? I never figured this out. I would get it upgraded, and the website would show 6.4.14, and as soon as the busybox container would run/restart, it would somehow downgrade to 6.4.1 again. I see a lot of people on these forums struggling to upgrade/maintain their installations of Zabbix. At this point I would rather find documentation on how to export/import to a new Ubuntu/install that doesn't use Docker/compose.

[jhboricua]

It's really simple. First off, as a general rule, using :latest is a bad idea. You should be using specific versions of the docker images and only upgrading to a new one once you have gone over the release notes to make sure there are not any potential breaking changes.

Then it should be as simple as updating the version number you want to go to in the appropriate file, then do 'docker compose pull' followed by 'docker compose up -d' which will stop and restart the zabbix services defined in the compose file using the newer image version.

Now, it sounds as if you are using the compose files in the zabbix docker git repo. The reason git complains about commit changes when you try to pull again is probably because you have customized some of the compose/env files. By stashing you are removing those changes, which is probably messing up your deployment. There should not be a need to do another git pull. Just update the variable in the .env file from that repo that the compose file use with the image version you want to go to and do the 'docker compose pull && docker compose up -d' command to restart the containers using the new image version.

That said, You are better off creating your own compose files rather than relying on those. IMHO, the compose files in the Zabbix repo are needlessly complicated.