Container/image "busybox", what is it?

[t7MevELx0]

I was able to upgrade to the latest build of Zabbix 6.4.14 using the compose file.

It updates the three containers that actually do something:




IMAGE & NAMES
zabbix/zabbix-web-nginx-mysql:ubuntu-6.4-latest
zabbix-docker-zabbix-web-nginx-mysql-1

zabbix/zabbix-server-mysql:ubuntu-6.4-latest
zabbix-docker-zabbix-server-1

mysql:8.0-oracle
zabbix-docker-mysql-server-1




There's this fourth container I can't much information on, but if I didn't use docker rm to remove it, it would keep rebuilding the above three with older images every time it randomly ran.

IMAGE & NAME
busybox
zabbix-docker-db_data_mysql-1

I was able to find one mention of it online:

https://forums.docker.com/t/cannot-run-zabbix-docker-compose-job/129065/4

The one person on that forum says this container does absolutely nothing. I tried to see if it was generating logs and it was not. All this thing does is randomly start, mount a folder, and do absolutely nothing with it.

Was it safe to remove? It doesn't appear to actually do anything. Zabbix is still running fine without it.

Was this a leftover container/image from a previous version that was never cleaned up? I image it was fine to remove since the product is still working well.

[markfree]

There was a "composer redesign" on dec/2023 that added this "db-data" container, but there isn't much information about it.

This points to a compose file "compose_databases.yaml" with the Busybox image.

db-data-mysql:
image: busybox
volumes:
- ${DATA_DIRECTORY}/var/lib/mysql:/var/lib/mysql:rw

It uses the same MySQL DB directory. Postgres also uses a similar image.

I wouldn't remove it.

[sabe]

I had a same question and I removed db-data-mysql service from compose file. so far I don't see any issue.

[t7MevELx0]

I removed the busybox container, but it came back. It also randomly downgraded my installation from 6.4.14 to 6.4. I have no idea what's going on, but I can't get the upgrade to stick. It keeps reverting somehow. Like an old compose file is somehow being called on. Not only is it reverting, it's going from an Ubuntu based image back to an Alpine based image.