-
-
Notifications
You must be signed in to change notification settings - Fork 943
feat: adds docker swarm support to docker-containers
widget
#517
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
base: dev
Are you sure you want to change the base?
Conversation
- fix: error messages - refactor: uses map for latest tasks - fix: task sorting
I tried updating the task sorting to fix this. Not 100% sure it'll work but you can try the updated image If it still doesn't work, could you run this script on a manager node and paste it into a pastebin or something? Feel free to redact any PII. From your screenshot, you should be able to run something like Then, I can mock it up locally and figure out what went wrong. |
Issue remains after task sorting update. information from query.sh: In a swarm I don't think the Created and Updated timestamps are a reliable way of determining whether a service is healthy or degraded. It would depend more on the scheduling mode of the service:
|
Ahh that makes sense. I'll give that a shot. |
New image available. I definitely agree that the scheduling is the way to go. |
I wanted to see docker swarm support (#403) so this is my attempt at that. I ended up just reusing the
docker-containers
widget with amode
property to switch between the two.The config looks like this:
The result looks like this:

(left = mode: "standalone", right = mode: "swarm")
Docker Container for testing:
ghcr.io/kuhree/glance:pr-517
Happy to make changes or adjustments.