a year ago
I am trying to mount my volume to /var/lib/mysql but the server keeps crashing because there is data in the directory and it aborts.
6 Replies
a year ago
Hi there - I think you need to ensure that the /var/lib/mysql directory is empty before mounting the volume. What's in that directory currently / how is it being used?
Status changed to Awaiting User Response Railway • about 1 year ago
sarahkb125
Hi there - I think you need to ensure that the `/var/lib/mysql` directory is empty before mounting the volume. What's in that directory currently / how is it being used?
a year ago
I have no idea. It is a fresh deployment, so there shouldn't be anything. It is the default directory for mysql data, so I don't understand why it won't work.
How can I even see the contents of the directory? There is no way to access the file structure.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Hello,
For MySQL 5.7 you want to mount your volume to /var/lib/mysql and use the following start command -
docker-entrypoint.sh mysqld --innodb-use-native-aio=0 --disable-log-bin --performance_schema=0 --ignore-db-dir=lost+found --bind-address=::Status changed to Awaiting User Response Railway • about 1 year ago
brody
Hello, For MySQL 5.7 you want to mount your volume to `/var/lib/mysql` and use the following start command - ```plaintext docker-entrypoint.sh mysqld --innodb-use-native-aio=0 --disable-log-bin --performance_schema=0 --ignore-db-dir=lost+found --bind-address=:: ```
a year ago
thank you! that seems to have worked! how was i supposed to get that info? just so i know for the future...
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Brody's a mysql pro, comes from being in the trenches 🙂 glad the fix worked!
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved sarahkb125 • about 1 year ago