Closed 11jwolfe2 closed 3 years ago
Looking at it i think you data volume
volumes:
- ./data/mysql:/var/lib/mysql
Should be
volumes:
- /data/mysql:/var/lib/mysql
I have made this change with no resolve.
Not sure, its maybe your storage engine. What are you using?? NFS, iSCSI, BTRFS??
NFS, which works with all other docker containers I run. I am trying to use the NGINX-PROXY Manager for Raspberry pi with this as the DB. I never had it set to use persistence, but had an SD card fail and would like to use persistence to save with setup time in the future. For reference this is the docker container I am using and the video I used for setup.
Container: https://github.com/jlesage/docker-nginx-proxy-manager
I use NFS also.
What are you using for orchestration? K8S?
I have docker running on my rpi, and it can be managed with portainer as I have a client running on the pi. I am not using kubernetes. The NFS share is on an Open Media Vault NAS.
I would probably check your permissions;
I use Read/Write privileges No Squash Mapping Asynchronous Yes Non-Privileged port Allowed Cross-Mount Allowed
These are the permissions I have set up rw,no_root_squash,insecure,async,no_subtree_check,anonuid=1000,anongid=1000
Try the new 10.5.8 image and see if this resolves your problem.
I am trying to use this with a persistence file. so when I add the Volumes tag and a file allocation it errors out and shuts down. Any ideas why this would be happening?
I do not get this error when not specifying a volume.
Docker compose file:
mysql: image: 'yobasystems/alpine-mariadb:latest' environment: MYSQL_ROOT_PASSWORD: 'npm' MYSQL_DATABASE: 'npm' MYSQL_USER: 'npm' MYSQL_PASSWORD: 'npm' volumes:
Error log: