mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-09 03:09:38 +03:00
Bookstack is unable to connect to MariaDB #5467
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 @wachtell on GitHub (Oct 23, 2025).
Describe the Bug
Suddenly the bookstack-mariadb-0 container stopped working is giving this error:
kubectl logs bookstack-mariadb-0
Defaulted container "mariadb" out of: mariadb, preserve-logs-symlinks (init)
Error from server (BadRequest): container "mariadb" in pod "bookstack-mariadb-0" is waiting to start: PodInitializing
Steps to Reproduce
Error: kubectl logs bookstack-mariadb-0
Defaulted container "mariadb" out of: mariadb, preserve-logs-symlinks (init)
Error from server (BadRequest): container "mariadb" in pod "bookstack-mariadb-0" is waiting to start: PodInitializing
Expected Behaviour
That the bookstack server would connect to the database.
Screenshots or Additional Context
No response
Browser Details
Firefox Windows 11
Exact BookStack Version
BookStack v25.07.3
@ssddanbrown commented on GitHub (Oct 23, 2025):
Hi @wachtell,
This'll be quite setup/environment dependant, so can you detail your environment. What containers are you using? What host OS/service are you using? Can you provide any config/commands you're using? etc...
@wachtell commented on GitHub (Oct 24, 2025):
@ssddanbrown Thank you for reaching out. Bookstack is set up in Kubernetes on an Ubuntu 24.04 cluster using Helm.
@ssddanbrown commented on GitHub (Oct 24, 2025):
@wachtell commented on GitHub (Oct 27, 2025):
Bookstack:
ghcr.io/linuxserver/bookstack:version-v25.07.3
Database container:
bitnami/mariadb:11.4.4-debian-12-r0
Yes, it happens when I re-init the stack.
The logs I get:
kubectl logs bookstack-mariadb-0
Defaulted container "mariadb" out of: mariadb, preserve-logs-symlinks (init)
Error from server (BadRequest): container "mariadb" in pod "bookstack-mariadb-0" is waiting to start: PodInitializing
Do you think the container is corrupted?
@ssddanbrown commented on GitHub (Oct 28, 2025):
It's hard to determine what's going on as there's no application/container specific information with that provided error message at all, it's just information at the K8s layer.
You could try ensuring containers are stopped, then take a copy the mariadb container volume data, then attempt to use that via a standard docker run command using the exact same container image version.
That can confirm if the data is okay, or help provide more detailed errors in its logs.
Of course, ensure everything is backed up before attempting anything.
@wachtell commented on GitHub (Nov 12, 2025):
@ssddanbrown Thank you for reaching out to me. After researching, I realized that the reason the mariaDB did not initialize was that Helm calls bitnami/mariaDB. However, bitnami/mariaDB has since late September gone into legacy and is replaced by bitnamisecure/mariaDB. Once I replaced the image, everything worked fine. Go figure :-)