mariadb container does not start mariabdb service while dockerhost have a public ip, everything else looks good. The volume is visible the netapp trident 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 tried to create the volume while dockerhost has its Internet IP but in this case unix permissions are wrong
bash-5.1# ls -ld /var/lib/mysql
drwxrwxrwt 2 mysql mysql 4096 Sep 20 13:39 /var/lib/mysql
we are not using kubernetes only docker, docker-compose with netapp 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
First of all, please, indent your compose yaml properly in the code block. If you share an invalid yaml you make it harder to everyone to understand it.
The issue you descrive doesn’t make sense to me. An IP address of the host has nothing to do with file permissions and how a container starts. You also use an outdated docker compose (switch to compose v2) and an old Docker engine. At least I guess it is the docker engine version you shared.
Please, format your post according to the following guide: How to format your forum posts
In short: please, use </> button to share codes, terminal outputs, error messages or anything that can contain special characters which would be interpreted by the MarkDown filter. Use the preview feature to make sure your text is formatted as you would expect it and check your post after you have sent it so you can still fix it.
Example code block:
```
echo "I am a code."
echo "An athletic one, and I wanna run."
```
After fixing your post, please send a new comment so people are notified about the fixed content.
sorry about the single posts. The Application said new user can only post 2 links. Thats why
root@debian12test:~/guacamole# dpkg -l | grep docker
ii docker-compose 1.29.2-3 all define and run multi-container Docker applications with YAML
ii docker-compose-plugin 2.29.7-1~debian.12~bookworm amd64 Docker Compose (V2) plugin for the Docker CLI.
ii docker.io 20.10.24+dfsg1-1+b3 amd64 Linux container runtime
ii python3-docker 5.0.3-1 all Python 3 wrapper to access docker.io's control socket
ii python3-dockerpty 0.4.1-4 all Pseudo-tty handler for docker Python client (Python 3.x)
I don’t know this volume plugin, but have you tried if it works, if you use it with vanilla docker-ce from docker’s repositories?
You can install it following these instruction: https://docs.docker.com/engine/install/debian/
The packages of os maintainers may or may not be modified to align with the philosophy of the distribution.
If it does not work with vanilla docker-ce, I would suggest asking the maintainer of the volume plugin about the behavior you experience. If a volume plugin is used, docker delegates the management to the plugin itself.