docker-compose example does not work as-is #46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
i've been trying to get the docker-compose example running, but for whatever reason i can't get it to work.
https://codeberg.org/bookstack/devops/src/branch/main/config/lsio-docker/docker-compose.yml
I followed the link on https://www.bookstackapp.com/docs/admin/installation/ which led me here.
here are the steps i followed
mkdir bookstack_db_dataandmkdir bookstack_app_datadocker-compose.ymlas linked aboveAPP_KEYwith the output from the commanddocker run -it --rm --entrypoint /bin/bash lscr.io/linuxserver/bookstack:latest appkeydocker-compose up -dresulting error (logs from bookstack container)
No visible errors from mariadb.
Not sure if i'm missing anything but I would expect the example to work as-is.
using synology dsm fwiw
Hi @OscarLundberg,
Can you try:
Helps rule out any potential timing issues.
I could try it that way, although I did already try to delete only the bookstack container and volume dir, and then re-run
docker-compose up -d. I could see that mariadb was not recreated and was up and running when bookstack started, but I had the same error occur again.I also tried to connect manually via
mysqlcommand, from the bookstack container to mariadb, and it seemed to just time out there too. I tried to ping mariadb and it resolved the IP but I got no packets back (that may be expected though, idk)If you can't reproduce it it's probably some nonstandard network thing on my end, but other compose projects without any network config seem to work, tried wiki.js now for example (also has an app service and a db service, albeit postgres) and it seems to be running fine
Found this
https://www.reddit.com/r/synology/comments/sofxgf/having_trouble_with_docker_container_networking/
apparently DSM firewall interferes with docker networking, so this is not a fault of bookstack.
for the record wiki.js did have the same issue, it just failed more silently and allowed me to start up and log me in without the DB connection.