Closed monkybrain closed 5 years ago
Sorry, I jumped the gun there. Apparently the container is registered as up & healthy after the first health check. The problem is that the first health check isn't triggered until 5 min after the container has started. Would it be possible to decrease the interval to say 30s? Or make the interval an option?
Hi! Yes I'm aware of this issue and there's already an accepted PR which decreases the interval down to 30s for API module, the same will be done for "Web" module and released with next version.
In the meantime there's a nightly API build for Docker already available with this change tagged as "latest". I could do the same for Web module if it helps you. :)
That would be great! Thanks!
No problem, I just published the new Web build so feel free to use 'latest' images until version 0.6.0 is out :)
Great, thanks! I really appreciate the swift response.
Happy to help!
Hey! Unfortunately, I'm not gonna be able to finish all the things I meant for version '0.6.0' before December so I decided to roll out this fix a little sooner in a patch release with version '0.5.1'. Cheers!
Hey there, I have been facing the same issue when i am trying to run my selenium script in docker. It got stuck after health check Can anyone please help out?
Hey! I recently added Zoonavigator to a Docker Compose project and I can access the web ui without any problems. However, I've noticed that the containers never seem to get past the "starting" stage. If I run
docker-compose ps
I get the following output:This wasn't a problem until I started using Traefik, which doesn't register services until the starting stage has completed. Is there anything I can do here? Or is this a bug?
Btw, great project!