I’m working with Crank storyboard and reviewing their documentation here https://support.cranksoftware.com/hc/en-us/articles/360056955212-Building-a-Storyboard-Container. As you can see the version of your base image for wayland is out of date. How do I bring this file up to be current, so I can make my own container?
Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
To update the base image for Wayland in your Dockerfile to a current version while working with Crank Storyboard on Torizon, you will need to modify the Dockerfile to use a newer base image that is compatible with your requirements. Here are the steps to do so:
-
Identify the Current Base Image: First, locate the line in your Dockerfile that specifies the base image. It might look something like this:
FROM torizon/weston:<old-version-tag>The
<old-version-tag>represents the version of the Wayland base image that is currently being used. -
Find a New Base Image: Visit the Docker Hub or the registry where the Torizon base images are hosted to find a newer version of the Wayland base image. Look for tags that represent newer versions. The Toradex Docker Hub page or the official Torizon documentation can be helpful resources for finding updated images.
-
Update the Dockerfile: Replace the old version tag in the Dockerfile with the tag of the newer version you wish to use. For example:
FROM torizon/weston:<new-version-tag>Ensure that
<new-version-tag>is the tag of the newer version you found in the previous step. -
Build the Container: After updating the Dockerfile, build the container again using the
docker buildcommand. This will create a new Docker image based on the updated base image. For example:docker build -t your-custom-storyboard-container . -
Test the Container: Before deploying the updated container, it’s important to thoroughly test it to ensure that the new base image does not introduce any compatibility issues with your Crank Storyboard application.
By following these steps, you can update the base image for Wayland in your Dockerfile to a current version, allowing you to make your own container with updated dependencies. It’s always a good practice to review the release notes or documentation of the new base image for any changes that might affect your application.
Best regards, Toradex AI Assistant
Please, also check if these links can help you solve your problem:
Partner Demo Container - Crank Storyboard | Toradex Developer Center.
Greetings @jeffbelz,
This Crank Storyboard container is quite old as you said. It hasn’t been updated in quite a while and was designed for a much older version of Torizon OS. Even if you change the base container image I’m not sure if it will run properly on current Torizon OS versions.
If you want to try, then just see the equivalent container image from this list here: List of Container Images for Torizon | Toradex Developer Center
In this case it would be torizon/wayland-base-vivante:3 (assuming you’re using some version of Torizon OS 6.X). That said this would only update the base container image, but it would not update all the things coming from the crank side. Which as I said were for an older version of Torizon OS.
I think Crank were looking at updating this old container. Though I don’t know what the state of this effort is. I could try and check with them if you want.
Best Regards,
Jeremias
torizon/wayland-base-vivante:3 is there a platform like arm64v8?
torizon/arm64v8-wayland-base-vivante:3?
You could check, I did ask them for the original docker file they used to make their container. Also, The old container does work on the the new Torizon OS. I have it running now.
I just needed to add something to the container to get gstreamer-backend working
torizon/wayland-base-vivante:3 is there a platform like arm64v8?
If you check this container image on Dockerhub: https://hub.docker.com/r/torizon/wayland-base-vivante
You’ll notice it only comes in arm64. That naming convention of putting the architecture in the container image name is something we used in the past.
Also, The old container does work on the the new Torizon OS. I have it running now.
Interesting. I recall others had issues with this old container image. I know the Crank stuff in this container is also not exactly their latest stuff, which isn’t ideal for some. In any case I went ahead and asked Crank if they have any plans on updating this container. As it’s probably more ideal to be using the latest stuff if possible.
Best Regards,
Jeremias
I was playing around tonight and one issue I ran into is it was saying my container was unhealthy. I narrowed it down and it’s for the west container version. Seems to be a big difference between
torizon/weston-vivante:2 and torizon/weston-vivante:3
there is a command and a health check for the docker-compose and the one that works for v2 does not work for v3. I guess what is the proper health check for v3?
I guess what is the proper health check for v3?
Well there’s many things you could do for a healthcheck. If you’re looking for an example we have stuff like this: torizon-samples/gstreamer/bash/simple-pipeline/docker-compose.arm64.yaml at bookworm · toradex/torizon-samples · GitHub
This basically just tests for the existence of the wayland-0 socket file. In most cases if this socket exists that’s a pretty good indication that Weston has started and is running properly.
Best Regards,
Jeremias
HI @jeffbelz,
Here is Max I am a FAE at Crank Software. I have been working recently to update these Containers.
although this is still WIP, I have a functional container for the IMX8 and the TI62 (Imx6 and Imx7 WIP) for Torizon OS 6.x.y
I also put together an integration guide. It all can be found on my personal GitHub Repository
This will be moved to the Crank Official repository soon
please reach out to us if you have any question. (there is a link to support at the end of the readme file)
kind regards,
Max
1 Like