I created my first yocto reference torizon image by running the Docker Crops container and this executed fine.
However when i try to deploy my device (via the Torizon Core Builder, version 3.12.0) i always result in a docker pull request error with a terminal message of a partial pull, similar to this (not my image but same error).
Image unpacking (newly created Tezi tarball, version 7.1.0)
Image deploy
Results in docker pull error.
The same workflow with my previous build (Tezi 6.7.0) works fine so i think there is something wrong the with the way i build my new 7.1.0 image.
For the record, i did not make any changes to the docker crops image whatsoever, the docker command i ran was the following:
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
It sounds like you’re encountering a Docker pull request error while trying to deploy your custom Torizon image using TorizonCore Builder. Let’s go through some steps to help you troubleshoot and resolve this issue:
Network Connectivity: First, ensure that your device has a stable internet connection. Docker pull requests need access to the Docker registry, and any network interruptions can lead to partial pulls.
Docker Daemon Status: Check that the Docker daemon is running correctly on your system. You can verify this by using the command systemctl status docker or docker info to ensure Docker is operational.
Image Availability: Make sure the image you are trying to pull is available in the Docker registry. Double-check the image name and tag to ensure they are correct and that the image is not private or restricted.
Registry Credentials: If the image is hosted on a private registry, ensure that your Docker client is logged in with the correct credentials. You can use docker login to authenticate if necessary.
Docker Configuration: Review your Docker configuration for any proxy settings or restrictions that might affect the pull request. Adjust these settings if needed.
Retry the Pull: Sometimes, simply retrying the pull request can resolve transient issues. Try using the docker pull command manually to see if the issue persists.
If these steps do not resolve the issue, consider checking the Docker logs for more detailed error messages that could provide further insight into the problem. You can do this using docker logs <container_id> for any running containers or by checking the system logs for Docker-related entries.
I hope these steps help you resolve the Docker pull request error during your deployment process.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
First of all just to clarify you said the issue is a “docker pull” error, but your screenshot shows an “ostree pull” error instead. So is it an issue with Docker or OSTree?
If it is an OSTree error and the screenshot is accurate. Then, this is a rarely seen issue that has popped up very few times in the past. The issue is we were never able to reproduce this even somewhat regularly so we never learned enough about the issue to do anything about it. For nearly every case though the issue would seem to go away after starting things from scratch.
Just as a sanity test, if you rebuild your Yocto image and then try the process with TorizonCore Builder again, do you still get this same error?
my apologies, it is indeed an Ostree error and not a docker error, i got mixed up there.
I’ll check to rebuild the yocto image again today and if that does not work i’ll try a complete rebuild from scratch.
if this is the error which pops up every now an then is there any configuration setup you’d like me to check or inform you about before i retry?
Update:
Before i rebuild the complete image i tried to redeploy a few times using torizoncore builder and i got it to actually deploy the image.
I think the main reason i got it to deploy was that i stopped the running '‘EASY PAIRING’ containers on the module before trying to deploy again.
I added the logs where i tried several times, tried to connect to SSH to verify a connection was possible and stopped the running docker containers on the module. TCB_log.txt (20.8 KB)
I tried the same image deploy again and this also worked.
After that i tried my own custom image (custom device tree build via Torizon Core Builder which i also use for Torizon 6.7.0. build and completes correct there), this now deploys also correctly and reboots the module, but after the reboot the module hangs at ‘Starting Kernel’.
I also added this log for reference (module console log). Module boot log, Custom Tezi 7.1.0. build.txt (2.9 KB)
Are there discrepancies in the usage of torizon core builder for Torizon 6 and 7 which can cause these type of errors?
Just realized i am running Linux source for TI Linux 6.1.y with the Torizon Core Builder (device tree overlay source), do i need to update this to another branch/version for torizon 7?
Update 2:
For every body with the same/or similar ssue.
This was indeed the cause of the freezing kernel, i updated the device tree source to kernel version 6.6.58 (for Torizon 7.1.0) and then it did boot.
The problem showed itself as a kernel boot message hanging on the
“Starting kernel …”
message and never going any further.
After updating my device tree source repo from 6.1.83 Kernel version for Torizon 6 to Kernel version 6.6.58 for Torizon 7.1.0 it worked.
Torizon release matrix
Glad you were able to resolve these issues. Also yes please do take care when dealing with different major versions of the OS (i.e 7.X vs 6.X). In semantic versioning the major version almost always denotes a breaking/major change to the system. In our case this usually means completely different versions of the Linux kernel.
Mixing versions will most likely cause issues like what you saw here.
