I am testing the updating with Torizon Cloud for my application container and i have 2 units setup in a fleet. I am seeing a problem where once the first update is succesfull (started via torizon cloud) and resulted in both units updated correctly, if i update again (to a higher version) both units fail the update with actualizr logs stating docker login has failed.
see log below:
On the first unit i logged back into docker and i get a successfull login result and retry the update from the cloud but it again fails with the same reason (docker login fail).
on the second unit i executed ostree admin cleanup since this helped me with a previous problematic situation. but after a retry this still fails with the same reason.
I am at a loss here why the update seems to fail after the initial success.
Are there some steps required after a torizon container update (e.g. reboot system, clearing old data or similar).
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello Richard,
Thank you for reaching out with your issue regarding Torizon Cloud updates. It sounds like you’re encountering a ‘docker login failed’ error after a successful initial update. Let’s go through some steps to help resolve this:
Verify Docker Credentials: Double-check that the Docker credentials are correct and have not expired. You can manually log in using docker login on each device to ensure the credentials are valid.
Network Connectivity: Ensure both units have a stable internet connection. Network issues can sometimes cause authentication failures if the devices cannot reach the Docker registry.
Configuration Review: Confirm that the Docker registry URL and credentials are correctly configured in both Torizon Cloud and on the devices.
OSTree Cleanup: You’ve already tried ostree admin cleanup, which is a good step. Ensure there are no residual artifacts from previous updates that might interfere with the current process.
Reboot Devices: A simple reboot can sometimes resolve transient issues. Try rebooting the devices after making any changes.
Logs and Diagnostics: Examine the logs from Aktualizr-Torizon and Docker for any additional error messages or warnings that might provide more context on the failure.
If these steps do not resolve the issue, consider any recent changes to your Docker registry or network environment that might affect authentication. Also, ensure your Torizon platform and Docker client are up to date, as updates can sometimes fix known issues.
I hope these suggestions help you resolve the problem. If you have any further questions, feel free to ask.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
Based on the logs you provided it sounds like the update client does not have access to the docker image registry where your container image is stored. Can you confirm that the container registry richard537/gateway_unit_application is a private registry?
Yes the registry is indeed private, for context i did not make the registry myself but the torizon IDE extension dit this for me (on dockerhub), as far as i know i did not enter an option for public/private registries somewhere.
It is nice that is automatically creates a private registry so no issues there.
