mariadb service does not start with trident volume while dockerhost have public IP

qSkills — Mon, 07 Oct 2024 09:36:23 GMT

im not sure to start this discussion on the right place. I havent found trident

mariadb container does not start mariabdb service while dockerhost have a public ip, everything else looks good. The volume is visible the volume is mapped into the container to /var/lib/mysql. Data is accessible. Rights are correct. Volume is read write.
the container is running only the mariadb service doenst come up. Changing the dokerhost IP back to internal ip
the mariadb service starts without any issues.

we are not using kubernetes only docker, docker-compose with trident plugin

Trident version: latest from this month
Container runtime: 20.10.24+dfsg1, build 297e128
docker-compose version: version 1.29.2, build unknown
OS: Debian12
NetApp backend types: Netapp AFF A400

To Reproduce
changing dockerhost to public ip

trident config

{
"version": 1,
"storageDriverName": "ontap-nas-economy",
"storagePrefix": "trident_eco_prod_labs_",
"managementLIF": "172.16.21.100",
"dataLIF": "172.16.21.31",
"svm": "corp_trident",
"username": "USER",
"password": "PASSWORD",
"aggregate": "n01_aggr1",
"limitVolumeSize": "300g",
"log-level": "debug",
"debug": true
}

docker-compose.yml

---
services:
guacd:
image: guacamole/guacd
networks:
- local

guac-serve:
image: guacamole/guacamole
links:
- guacd:guacd
- mariadb:mysql
ports:
- 8080:8080
environment:
- MYSQL_LOG_CONSOLE=true
- MYSQL_HOSTNAME=mariadb
- MYSQL_DATABASE=guacamole
- MYSQL_USER=guacamole
- MYSQL_PASSWORD=PASSWORD
- GUACD_HOSTNAME=guacd
- GUACD_PORT=4822
networks:
- local

mariadb:
image: mariadb:11.5
environment:
- TZ=Europe/Berlin
- MYSQL_ROOT_PASSWORD=PASSWORD
- MYSQL_DATABASE=guacamole
- MYSQL_USER=guacamole
- MYSQL_PASSWORD=PASWORD
volumes:
- debian12_guacamole:/var/lib/mysql
networks:
- local

volumes:
debian12_guacamole:
driver: trident_eco:latest # Ensure this matches your plugin name
# driver_opts:
# size: "30G"

networks:

local:
driver: bridge

Re: mariadb service does not start with trident volume while dockerhost have public IP

PravinKumar — Thu, 10 Oct 2024 05:56:48 GMT

Trident task is to provision volume, as I see from your update it is working as expected.
Container mariadb service goes down while changing docker host to Public IP, needs to be investigated from Kubernetes side.
If any further assistance on this on Trident perspective, request you to open support case with us.

Thanks and Regards,

Pravin Kumar

topic mariadb service does not start with trident volume while dockerhost have public IP in ONTAP Discussions

mariadb service does not start with trident volume while dockerhost have public IP

Re: mariadb service does not start with trident volume while dockerhost have public IP