Bookstack deleting data after docker-compose down #87
{{title}}
|
Hello, Here is my docker-compose file. `services: epbookstack: image: lscr.io/linuxserver/bookstack:latest container_name: epbookstack environment: - PUID=1000 - PGID=1000 - TZ=America/Chicago - APP_URL=https://bookstacks.FAKEDOMAIN.com - APP_KEY=base64:3qjlIoUX4Tw6fUQgZcxMbz6lb8+dAzqpvItqHvahW1c= - DB_HOST=bookstack_mariadb - DB_PORT=3306 - DB_DATABASE=bookstackapp - DB_USERNAME=bookstack - DB_PASSWORD=bookstack0123 volumes: - ./bookstack_app_data:/config ports: - 6875:80 restart: unless-stopped depends_on: - bookstack_mariadb bookstack_mariadb: image: mariadb:latest container_name: bookstack_mariadb environment: - PUID=1000 - PGID=1000 - TZ=America/Chicago - MYSQL_ROOT_PASSWORD=Pass26Pass - MYSQL_DATABASE=bookstackapp - MYSQL_USER=bookstack - MYSQL_PASSWORD=bookstack0123 volumes: - ./bookstack_db_data:/config restart: unless-stopped` |
{{title}}
|
can you try using a full path rather than a relative path? |
{{title}}
|
You're using the official mariadb image, which doesn't use /config for its data, it uses /var/lib/mysql |
{{title}}
|
lol im blind to have missed that :D |
{{title}}
|
Is there anyway to move the data from /var/lib/mysql to /config? I'm have issues with finding this data. is it in the mariadb container or is it stored somwhere else since i dont have the file path correct. |
{{title}}
|
this is a bit out of scope for us, but you can't simply copy the data, you need to dump it (normal backup process) and then import it into the new container (normal restore process) the backup and restore processes are well documented for mariadb. with that said, there is nothing wrong with you using the official container either |
{{title}}
{{editor}}'s edit
{{editor}}'s edit
|
Thank you for the response. I actually figured it out! This video from dan at bookstack gave me enough info to solve my issue. Thank you guys for all your help! You pointed me in the right direction. |
{{title}}
{{editor}}'s edit
{{editor}}'s edit
|
@thespad let me try that. The official Lsio docker-compose example is wrong haha, that is where i started from. |
{{title}}
It's not wrong though? that's different to your compose.
|
{{title}}
{{editor}}'s edit
{{editor}}'s edit
|
Is it because I'm pulling from the official image instead of image: lscr.io/linuxserver/mariadb:11.4.4 I'm not sure how that changed if i did change that. Should i change it back to lscr.io image? |
{{title}}
|
I should probably change it to the lscr.io/linuxserver/mariadb:11.4.4 just to be consistant. Another question is it easy enough to make a backup of the DB so i can move it to the new db. If so can someone help me with that. |
You're using the official mariadb image, which doesn't use /config for its data, it uses /var/lib/mysql