Database volume not mounting

[need4swede]

Database volume not mounting

[buckybytes]

You should be able to backup and restore your database using mysqldump

[ssddanbrown]

@need4swede Currently you data will be within the running container. Take care as that data will likely be destroyed if the container is destroyed (Which can occur even if you just take the compose stack down).

As mentioned by @buckybytes, you'd ideally perform a mysqldump of the existing data for safe-keeping, and re-import.
Alternatively, as long as you still use the same exact docker image, you could copy out the /var/lib/mysql files from inside the container. Ideally use a mysqldump though.

I've got a video here on taking a mysqldump via a docker compose stack.
See the "Creating Backups" and "Restoring a from a backup" sections.
It's using the linuxserver mariadb image, but the steps should be pretty similar.

[need4swede]

@ssddanbrown

Bless you, Dan. Worked like a charm!
Now excuse me while I document the backup process in my BookStackApp.

Cheers!

[ssddanbrown]

Hi @need4swede,
You are mounting the /config path for the database, which is commonly a linxuserver image thing, but not commonly used for other container images like the one you're using which is not a linuxserver-managed image.

Your compose stack indicates you're using this image.
Based upon the guidance there, I think you need to mount to the /var/lib/mysql container path instead for that image.

[need4swede]

Your compose stack indicates you're using this image. Based upon the guidance there, I think you need to mount to the /var/lib/mysql container path instead for that image.

Thank you for the reply! This seems to work and I can see my database folder now being used. Pardon my ignorance, but is there a way for me to transfer my existing database from the Docker volume to my host - or will I lose all my existing data and have to start fresh?