# get zabbix-docker repo git clone https://github.com/zabbix/zabbix-docker.git cd zabbix-docker # show current branch git branch
docker run --name Zabbix_MySQL
-v /volume1/docker/Zabbix/Zabbix-MySQL:/var/lib/mysql
-e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:latest
WARNING: Some services (zabbix-agent, zabbix-java-gateway, zabbix-proxy-mysql, zabbix-proxy-sqlite3, zabbix-server, zabbix-snmptraps, zabbix-web-apache-mysql, zabbix-web-nginx-mysql) use the 'deploy' key, which will be ignored. Compose does not support 'deploy' configuration - use `docker stack deploy` to deploy to a swarm.
Creating initialize_mysql-server_1 ... error
Creating initialize_zabbix-java-gateway_1 ...
Creating initialize_zabbix-snmptraps_1 ...
Creating initialize_db_data_mysql_1 ...
Creating initialize_zabbix-java-gateway_1 ... done
ERROR: for initialize_mysql-server_1 Cannot start service mysql-server: Bind mount failed: '/volume1/docker/Zabbix/initialize/zbx_env/var/lib/mysql' Creating initialize_db_data_mysql_1 ... error
Creating initialize_zabbix-snmptraps_1 ... error
' does not exists
ERROR: for initialize_zabbix-snmptraps_1 Cannot start service zabbix-snmptraps: Bind mount failed: '/volume1/docker/Zabbix/initialize/zbx_env/var/lib/zabbix/snmptraps' does not exists
ERROR: for mysql-server Cannot start service mysql-server: Bind mount failed: '/volume1/docker/Zabbix/initialize/zbx_env/var/lib/mysql' does not exists
ERROR: for db_data_mysql Cannot start service db_data_mysql: Bind mount failed: '/volume1/docker/Zabbix/initialize/zbx_env/var/lib/mysql' does not exists
ERROR: for zabbix-snmptraps Cannot start service zabbix-snmptraps: Bind mount failed: '/volume1/docker/Zabbix/initialize/zbx_env/var/lib/zabbix/snmptraps' does not exists
ERROR: Encountered errors while bringing up the project.
Further in the process could be handy:
# replace latest with 4.0.1 sed -i "s/-4.0-latest/-4.0.1/" docker-compose_v3_alpine_mysql_401.yaml
If you can't seem to get a remote system working with your synology LDAP server using secured LDAP (LDAPS), you might have a certificate issue. Solving this is the best solution, however you might just disable the certificate checking on your client:
add to \etc\ldap\ldap.conf:
TLS_REQCERT never