Weston container unstable when running from docker compose file

Technical Support
, , ,
1

sb_exisitng.yml (1.4 KB)

Running Torizon OS 6x. The weston container will not stay open. Have no clue why. I got the first part of the compose file from gstreamer example in bookworm.

I guess if I wanted to launch “torizon/weston-vivante:3” from a compose file, how would I do it.

2

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?

:+1: :-1:

To launch the torizon/weston-vivante:3 container from a Docker Compose file, you need to ensure that your docker-compose.yml file is correctly configured. Below is an example of how you can set up your docker-compose.yml file to run the Weston container:

version: "2.4"
services:
  weston:
    image: torizon/weston-vivante:3
    container_name: weston
    network_mode: host
    environment:
      - ACCEPT_FSL_EULA=1
    volumes:
      - /tmp:/tmp
      - /dev:/dev
      - /run/udev:/run/udev:ro
      - /var/run/dbus:/var/run/dbus
      - /etc/machine-id:/etc/machine-id
      - /run/user/0:/run/user/0
      - /home/torizon/weston.ini:/etc/xdg/weston/weston.ini:ro
    devices:
      - "/dev/dri:/dev/dri"
      - "/dev/input:/dev/input"
    command: --developer weston-launch --tty=/dev/tty7 --user=torizon

Explanation of the Compose File:

  • version: Specifies the version of the Docker Compose file format.
  • services: Defines the services that will be run.
    • weston: The name of the service.
      • image: Specifies the Docker image to use (torizon/weston-vivante:3).
      • container_name: Sets a custom name for the container.
      • network_mode: Uses the host network mode for better performance and compatibility.
      • environment: Sets environment variables. ACCEPT_FSL_EULA=1 is required to accept the Freescale EULA.
      • volumes: Mounts various directories and files from the host to the container.
        • /tmp:/tmp: Shares the /tmp directory.
        • /dev:/dev: Shares the /dev directory.
        • /run/udev:/run/udev:ro: Shares the /run/udev directory as read-only.
        • /var/run/dbus:/var/run/dbus: Shares the D-Bus socket.
        • /etc/machine-id:/etc/machine-id: Shares the machine ID.
        • `/run/user/0:/run
3

Greetings @jeffbelz,

Well I just took your docker-compose file exactly as provided and ran it on my Verdin i.MX8M Plus running Torizon OS 6.7.0. It works fine, container seems to stay up for the couple of mins I tested it. I did not notice any obvious issues, I can see the sample crank GUI with the car running.

When you test this did you make sure to stop all other containers on your system? Maybe something is interfering there?

When you say “will not stay open” do you mean the container just exits immediately? Any logs of any kind when this happens?

Best Regards,
Jeremias

4

well, today I tried it again and everything is fine. I did do a complete power down from yesterday to today. maybe something got botched. Weird, because I did do a reboot yesterday, but not a power cycle.

5

Glad to hear it resolved itself somehow. Perhaps it was just a strange transient issue or something. In any case let us know if it pops up again.

Best Regards,
Jeremias