Issue pre-providing containers for torizoncore

Technical Support
, , ,
#1

Hi,

I’m trying to follow this topic: Pre-provisioning Docker Containers onto a TorizonCore image

to provide container to a Torizoncore image and launch them at startup.

The issue I met is that every time I try to deploy my image to the target, the containers don’t seems to be transmitted.

I will explain it more in details:

I downloaded an adapted torizoncore image without container as indicated in the topic.

Then I Wrote this tcbuild.yml file:

input:
  easy-installer:
    local:  torizon-core-docker-apalis-imx6-Tezi_5.3.0+build.7.tar

customization:
  device-tree:
    include-dirs:
      - device-trees/include/
      - images/
    custom: device-trees/dts-arm32/imx6q-apalis-eval.dts
    overlays:
      remove:
        - apalis-imx6_parallel-rgb_overlay.dtbo
        - display-edt7_overlay.dtbo
        - apalis-imx6_stmpe-ts_overlay.dtbo
        - apalis-imx6_hdmi_overlay.dtbo
      add:
        - device-trees/overlays/apalis-imx6_eim_overlay.dts
        - device-trees/overlays/apalis-imx6_lvds_overlay.dts
        - device-trees/overlays/apalis-imx6_lvds_overlay2.dts
  kernel:
    modules:
      - source-dir: syctrl-eim-driver/
        autoload: no

output:
  easy-installer:
    local: custom
    name: "My customized image with container images"
    bundle:
      compose-file: docker-compose.yml

And I sent the build command:

$ torizoncore-builder build

The output indicates me that my containers are downloaded and extracted.
In the output dir, I find the following files:

LA_OPT_NXP_SW.html
SPL
docker-compose.yml
docker-storage.tar.xz
image.json
marketing.tar
prepare.sh
toradexlinux.png
torizon-core-docker-apalis-imx6.ota.tar.zst
u-boot-initial-env-spl
u-boot.img
wrapup.sh

The existence of the file “docker-storage.tar.xz” indicates me that my containers have been generated. especially since it weighs 255mb.

Then I unpack this image with the command:

torizoncore-builder images unpack custom/

And I union it:

torizoncore-builder union newImage

Then here is my deploy command (with password modified):

torizoncore-builder deploy newImage  --remote-host 192.168.xxx.xxx --remote-username torizon --remote-password xxx --reboot

My board reboot and the modifications made thanks to the overlays seems to be effective.
But when I type “docker images”, nothing appears.

If you have an idea don’t hesitate to share it to me.

Best regards,
rfonck

#2

Greetings @rfonck,

It seems you may have gotten the directions a bit mixed up. In the article you’re referencing we present to alternative options to pre-provision containers. One method uses the build command and the other uses the bundle and combine commands. You seem to have combined both methods in a way.

Also there seems to be a misunderstanding on how pre-provisioned containers get deployed to a board. After doing either method, you need to use Toradex Easy Installer to flash the image that was produced. Pre-provisioned containers can not be deployed over ssh.

In your usage you presented, you’d flash the output directory produced by the build command using Toradex Easy Installer. The deploy command is for deploying all TorizonCore Builder customizations except for pre-provisioned containers.

Best Regards,
Jeremias