Closed mariushosting closed 1 year ago
I have not used a super-recent version of the image, but from memory it would wait, and I could bring everything up at once. Looks like this would be the relevant part of the script.
Do you have positive confirmation that this is timing based? Just asking since the log error provided is not clear in that. Does everyone come up fine when you specifically start the database first?
I have not used a super-recent version of the image, but from memory it would wait, and I could bring everything up at once. Looks like this would be the relevant part of the script.
Do you have positive confirmation that this is timing based? Just asking since the log error provided is not clear in that. Does everyone come up fine when you specifically start the database first?
The linuxserver bookstack image immediately tries to connect to the database before the database starts and this cause the issue. I just switch to the solidnerd bookstack image to solve the issue. Solidnerd have a db waiting time set before connecting to the database.
You responded to and quoted a post that links to the piece of code that waits for the database and has an echo line Waiting for DB to be available
. Really?
Anyway. . .
It would be nice to see a full timestamped log to see if it waited and how long, as it printed that it was waiting.
Okay. For what it's worth, I just tested a fresh compose setup, using the latest images and using the compose setup provided in the readme here, and it all comes up fine.
I then did a further test by only raising the bookstack container via docker-compose up --no-deps bookstack
.
The startup script would wait here:
bookstack | Waiting for DB to be available
bookstack | nc: bad address 'bookstack_db'
bookstack | nc: bad address 'bookstack_db'
Then I'd start the DB container after a few seconds and it would then continue once the DB was up. So all looks functional on my side. (Ubuntu 22.10 / Ubuntu 22.10 / docker-compose version 1.29.2).
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Confirmed db wait is present and working, closing issue
Is there an existing issue for this?
Current Behavior
The current bookstack image have no database waiting time. So you need to restart the container to be able to connect to the database.
Expected Behavior
No response
Steps To Reproduce
The current bookstack image have no database waiting time. So you need to restart the container to be able to connect to the database.
Environment
CPU architecture
x86-64
Docker creation
Container logs