-
Notifications
You must be signed in to change notification settings - Fork 295
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
Auto-connect to hosts at interval #3044
Comments
This was asked before and discussed in #2969 tldr; Dozzle reconnects. However, at startup it does need a successful connection at least once. This works as designed to avoid misconfigurations. |
Also can you clarify what you mean by that? If a host is unavailable then Dozzle should show an error immediately. |
Hmm okay. I've seen Docker hosts disappear from this list entirely.
Dozzle does start, but there's a little delay compared to if the host was not added to Dozzle. I'm now aware of the flag that controls this. |
Ah interesting. I see why that could be confusing now. I didn't think auto updating would break when host is gone. I think using an agent might fix this. Could you read my proposal at #3052 and provide feedback? I think it would be a while before it's ready but I am looking for feedback. |
I'm closing this issue since I'm no longer facing this issue.
I don't have experience with k8s, sorry :( But I don't think removing this functionality is a good idea for users like me. |
Hello!
When a Docker host is unavailable at Dozzle startup, Dozzle takes time to become available due to unavailable hosts.
Also, when the host does eventually become available, it no longer shows in Dozzle.
I think Dozzle should start-up with available hosts with a short timeout and check for connectable hosts every x time interval, which could be made configurable.
Thanks!
The text was updated successfully, but these errors were encountered: