We’ve seen a “read: connection refused” from aktualizr trying to access https://registry-1.docker.io/v2/ the error is a little vague and I was hoping there is a way to see what the reason for refusal was. I think it could be because the connection dropped out, but we would like to know to rule out any potential issue. Running “docker login” and restarting the aktualizr resolved the iss. Is there any known issues that this could fix? alternatively can we get any extra information for the connection refusal from the system?
Greetings @DuncanNapier,
Could you give more information here please. For example could you share the rest of the Aktualizr logs so we have context for this “connection refused” message. Furthermore, what version of Torizon OS is this?
Also, when you saw this message were you doing a container update of some kind? Or do you just see this message when the system is idle?
Running “docker login” and restarting the aktualizr resolved the iss. Is there any known issues that this could fix? alternatively can we get any extra information for the connection refusal from the system?
If running docker login fixes the issue, then is Aktualizr trying to update and pull container images from a private registry?
As for more logging, I’m not sure. This message seems to come from Docker not Aktualizr, so increasing the log level of Aktualizr probably wouldn’t do much here. Though I suppose you can still try to increase the log level of aktualizr and see if it uncovers further information: Aktualizr - Modifying the Settings of Torizon Update Client | Toradex Developer Center
Best Regards,
Jeremias