[MDEV-29288] MariaDB Docker container on Created: 2022-08-10 Updated: 2022-08-11 Resolved: 2022-08-11 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Maduranga | Assignee: | Daniel Black |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | Compatibility, docker | ||
| Environment: |
Docker container using compose |
||
| Description |
|
Hi, I found a few issues related to this but couldn't nail anything down close to the exact matter describing below, hence creating a new ticket. This is about the MariaDB changing the permissions on the bind mount to a level such that it becomes read-only, then fails to write to the directory, resulting a failure. First block below is the error from the docker logs. Second is the compose file I used to build the docker containers.
Compose file:
Server OS information
Notes There are two containers created by the compose file. First is the MariaDB and second is the Apache HTTPD. |
| Comments |
| Comment by Daniel Black [ 2022-08-11 ] | |||||||||||||
|
What is the full permissions on ./wp_db (ls -laZ ./wp_db? What docker/container runtime version is being used? Is SynologyDS based closely on another Linux distro? | |||||||||||||
| Comment by Maduranga [ 2022-08-11 ] | |||||||||||||
|
Full permissions are as follows:
Despite what permissions I give to the folder that seem to change after a single run of the container.
Synology DSM Seem to say its a GNU/Linux. I suspect it could be a Debian distro, I don't have evidence on that.
| |||||||||||||
| Comment by Daniel Black [ 2022-08-11 ] | |||||||||||||
|
Something is removing the exec permissions on the mount point which makes it rather broken. Maybe its how its mounted. option:
The container doesn't remove exec permissions so sorry to say its something in your environment causing this. I hope one of the options provides a work around. |