mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-07-16 05:33:49 +03:00
Bookstack +docker + mariadb #5265
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Fabio-91 on GitHub (Apr 23, 2025).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
This deployment is part of a mockup test on a Synology NAS, aiming to evaluate BookStack in a self-hosted setup using Docker.
I’m deploying the application using two separate Docker containers via docker-compose:
bookstack_db (MariaDB, image: lscr.io/linuxserver/mariadb)
bookstack (BookStack, image: lscr.io/linuxserver/bookstack)
Both containers are connected via a custom Docker network named bookstack_net.
Volumes are locally mounted at /volume1/docker/bookstack.
❌ Errors Encountered
When launching the bookstack container, I get the following SQL errors:
SQLSTATE[HY000] [1045] — Access denied for user
SQLSTATE[HY000] [2002] — Connection refused
docker-compose.yml (Sanitized for clarity) :
version: "2"
services:
bookstack_db:
image: lscr.io/linuxserver/mariadb
container_name: bookstack_db
environment:
- PUID=1026
- PGID=100
- MYSQL_ROOT_PASSWORD=91-Montgeron-DB!
- TZ=Europe/Paris
- MYSQL_DATABASE=bookstackapp
- MYSQL_USER=bookstack
- MYSQL_PASSWORD=91-Montgeron-DB!
volumes:
- /volume1/docker/bookstack/db:/config
ports:
- 3306:3306
networks:
- bookstack_net
restart: unless-stopped
bookstack:
image: lscr.io/linuxserver/bookstack
container_name: bookstack
environment:
- PUID=1026
- PGID=100
- APP_URL=http://192.168.1.11:6875/
- APP_TIMEZONE=Europe/Paris
- DB_HOST=bookstack_db
- DB_PORT=3306
- DB_USER=bookstack
- DB_PASS=91-Montgeron-DB!
- DB_DATABASE=bookstackapp
- APP_KEY=base64:CClA6bWC3qhP6yMVQECyTblYtj7uAxOh0dDpi0BcZ5w=
volumes:
- /volume1/docker/bookstack/config:/config
ports:
- 6875:80
depends_on:
- bookstack_db
networks:
- bookstack_net
restart: unless-stopped
networks:
bookstack_net:
external: true
Exact BookStack Version
BookStack v23.12.1
Log Content
No response
Hosting Environment
pc tehcnique sur windows + NAS synoloy (DS216+II)
@Fabio-91 commented on GitHub (Apr 23, 2025):
Indeed, MySQL/MariaDB error 1045 (Access denied) can sometimes be resolved by enclosing the password in double quotes (").
"91-Montgeron-DB!"
@ssddanbrown commented on GitHub (Apr 23, 2025):
Hi @Fabio-91,
On recent linxuserver bookstack images, you should be using
DB_USERNAMEinstead ofDB_USER, andDB_PASSWORDinstead ofDB_PASS.As per #5587, you can use this recent reference compose file as a guide: https://codeberg.org/bookstack/devops/src/branch/main/config/lsio-docker/docker-compose.yml
@Fabio-91 commented on GitHub (Apr 24, 2025):
HI @ssddanbrown,
Update, I corrected the 2002 error by first deleting the default .env file located in ./bookstack_app_data/www/.env.
I then modified this file with my own parameters, and returned it to its original location.
After that, I checked the BookStack logs (./bookstack_app_data/log/bookstack/laravel.log), and the 2002 error had disappeared.
However, error 1045 still persists, even though I thought I'd fixed it by adding quotation marks around the password ("password").
@ssddanbrown commented on GitHub (Apr 24, 2025):
@Fabio-91 Environment variables set in the docker compose fill will take precedence over any
.envvalues.My suggestion (assuming this is a new instance) would be to start from fresh.
Delete all prior volumes/data/containers, then start again from our example compose file linked above.
You should not need to change any volume data files to get a working instance.
@Fabio-91 commented on GitHub (Apr 24, 2025):
@ssddanbrown
I started from scratch to do a test: I separated the two containers (BookStack and MariaDB), and strangely, it worked — no more MySQL-related errors. 👍
However, now I can't access the BookStack web page. The container is running fine, no visible errors, but nothing shows up when I try to open the URL.
Do you have any idea what I should check?
Here are the following screenshots to show the current situation:
User account:
Image:
Network:
UID:
Document:
MariaDB docker-compose.yml:
version: "3.8"
services:
mariadb:
image: lscr.io/linuxserver/mariadb
container_name: mariadb
environment:
- PUID=1026
- PGID=100
- TZ=Europe/Paris
- MYSQL_ROOT_PASSWORD=bookstack91421
- MYSQL_DATABASE=bookstack
- MYSQL_USER=bookstack
- MYSQL_PASSWORD=bookstack91421
volumes:
- ./db:/config
restart: unless-stopped
networks:
- bookstack_net
networks:
bookstack_net:
external: true
BookStack docker-compose.yml:
version: "3.8"
services:
bookstack:
image: lscr.io/linuxserver/bookstack
container_name: bookstack
environment:
- PUID=1026
- PGID=100
- TZ=Europe/Paris
- APP_URL=http://192.168.1.11:6875
- APP_KEY=base64:CClA6bWC3qhP6yMVQECyTblYtj7uAxOh0dDpi0BcZ5w=
- DB_HOST=mariadb
- DB_PORT=3306
- DB_DATABASE=bookstack
- DB_USERNAME=bookstack
- DB_PASSWORD=bookstack91421
volumes:
- ./app:/config
ports:
- 6875:80
restart: unless-stopped
networks:
- bookstack_net
networks:
bookstack_net:
external: true
To sum up, I now have two separate projects, each running a single container — one for MariaDB and one for BookStack.
@ssddanbrown commented on GitHub (Apr 24, 2025):
What exactly do you see when accessing via the browser?
@Fabio-91 commented on GitHub (Apr 24, 2025):
@ssddanbrown
@ssddanbrown commented on GitHub (Apr 24, 2025):
Is the firewall active on your synology box, and if so is port 6875 allowed through it?
@Fabio-91 commented on GitHub (Apr 24, 2025):
@ssddanbrown
I dont have firewall.
Does the nas need to be connected to the internet to display the web page?
@ssddanbrown commented on GitHub (Apr 24, 2025):
@Fabio-91 No, you just need to be on the same local network. Is
192.168.1.11the IP address of the NAS?@Fabio-91 commented on GitHub (Apr 24, 2025):
@ssddanbrown
Yes 192.168.1.11 is my NAS address.
@ssddanbrown commented on GitHub (Apr 24, 2025):
Okay. In that case I'm not sure thy you can't connect assuming you're on the same local network.
I'm not familiar enough with the options and behaviour of Synology docker management to know what might be the issue.
Maybe it's the network type used for the BookStack container? Does it state the network type anywhere?
Also, is the port mapping retained after container creation? If you look at the BookStack container can you see the port mapping anywhere in the UI?
@Fabio-91 commented on GitHub (Apr 25, 2025):
@ssddanbrown
It turned out the issue was related to the network configuration.
I created a custom Docker network from the command line (sudo docker network create bookstack_net), and it was assigned the subnet 172.20.0.0.
After attaching my containers to this new network, everything started working properly.
Thanks a lot for your help!
@ssddanbrown commented on GitHub (Apr 26, 2025):
Good to hear you got things working! Will therefore close this off.