-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dozzle 8.6.1 : Container is consired as stopped by Dozzle, while it is correctly running #3337
Comments
PS: I tried to restart docker-desktop does it does not fix the problem. |
Note : Updating to latest version of docker-desktop does not change anything. Here is docker system info output with the latest version:
|
This sound like a bug from Dozzle. But am not sure what is causing it and how come to no one else has reported it. I also use Dozzle everyday and haven't ran in to this issue.
Yes, that is very strange. The
That's even more strange because if it was a bug then Dozzle should at least be reset. What I think is happening is that at some point of the containers goes to a state and Dozzle doesn't know how to handle it. Dozzle has it's own memory database for performance and I am wondering if it is becoming out of sync some how. But restart Dozzle would presumably fix that. Your logs look fine. I think the best idea I can think of is creating a random API like Before doing that, can you think of a way I can reproduce this? Doesn't seem so since I haven't really seen it happen. |
@omasseau Try Send me that and tell me which container is not working. If the data looks right, then it is most likely a UI bug. |
@amir20 Thanks, I will do that asap ;) |
Here it is : The problematic container is : The result of /api/debug/store : |
I am guessing |
Another example : The problematic container is : The result of /api/debug/store :
|
Hm ok. So How are you getting in this state by the way? Are you tearing down containers and recreating them? I am looking at the code. |
I'm just doing a simple : The docker-compose.yml contains services which are activated through profiles. And in my docker-compose.yml I have associated profiles declared like that :
I'm gonna try by not providing profiles just to see if it changes anything. |
I can confirm it is not related to using docker compose with profiles. I have the same problem when starting the containers with a simple |
FYI, I just tried with amir20/dozzle:v7.0.7 and it works fine (all other things being equal). |
I also have a |
Can you do I don't even see a |
docker system event output : |
You clearly have I don't understand. I am going to add more debugging. Hold on. |
Wait, I think I know what it might be. |
OK, I think you have Dozzle as part of a larger compose file. That would make sense because, on startup, I only check running containers. However, if a container is transitioning from created to started, it is not captured. I tried to fix that in #3338. Can you pull |
@amir20 Indeed Dozzle is one the of the services declared in the compose file. |
Woohoo. Nice find. I'll merge. |
New version released. It also makes sense why most people didn't report this because I think most people are running Dozzle as a separate stack. |
π Check for existing issues
How is Dozzle deployed?
Standalone Deployment
π¦ Dozzle version
8.6.1
β Command used to run Dozzle
π Describe the bug / provide steps to reproduce it
When displaying Dozzle page, one of my container is shown as stopped, while it is running.
I never had this problem with version 7 of Dozzle.
Here you can see the running containers in docker-desktop :
You can clearly see that the container 'bdoc-gateway-proxy-1' is running.
Now if I go in Dozzle, you can see it is not listed :
If I ask Dozzle to show stopped containers, then the container appears in the list :
Strangely it is shown in white and not grey like should be a stopped container (like the 'esignature-1' container which is correctly detected as stopped).
For information, the container that is consirered as stopped seems random. It is not always the same.
Note that
docker ps
command correctly shows the container :So does
docker stats
:π» Environment
πΈ If applicable, add screenshots to help explain your bug
No response
π If applicable, attach your Dozzle logs. You many need to enable debug mode. See https://dozzle.dev/guide/debugging.
The text was updated successfully, but these errors were encountered: