Which containers failed to check for updates?

[henryxrl]

When checking for updates, I sometimes see a message like:

All containers are up to date (2 failed to check)

However, it doesn’t indicate which containers failed to check.

I’d like to understand:

• Which containers failed?
• Is there a way to view the detailed error?
• Are there logs or a debug mode that shows which containers could not be checked?
• Does this typically relate to registry auth, network timeouts, or something else?

Right now it’s hard to troubleshoot since I don’t know which containers are affected.

Maybe showing a clickable list of failed containers, or surfacing the specific error per container, would make troubleshooting much easier.

Thanks!

[Hustleberry]

Encountering this problem too and I am totally lost on how to find it...

[SterlynKong]

I can report the same message when I attempt an update. I cannot tell which two containers fail to check.

[thomaskrampe]

I'm having the same problem here. The only thing I see in the dockhand log is that there is an error, but there's no indication of which container it's related to.

=== SUMMARY ===
Total containers: 9
Checked: 8
Updates available: 1
Errors: 1

In my case, the problem only occurs on a host connected via Hawser Edge Connection; maybe that helps. Btw. pruning the environment doesn't help here.

[thomaskrampe]

Seems to be solved with v1.0.22