Deploying Yodeck Web Player

Overview

The native Yodeck Player is not documented as an ALPON target. This guide instead runs the Yodeck Web Player in Chromium on a display connected to an ALPON X5 AI or ALPON X4. The container is built from Alpine, runs Chromium as a dedicated kiosk user, and connects to the host X server through the X11 socket and an Xauthority file that you create on the device.

The steps below are identical on ALPON X4 and ALPON X5 AI.

1. 1

   Build the Yodeck Web Player container

   Create an arm64 container that runs Chromium as a non-root user and connects to the host X server. Open a terminal on your build machine, create a new file named Dockerfile, and add the following content:

   Dockerfile

   FROM alpine:3.21
   
   RUN apk add --no-cache chromium \\
       && addgroup -g 1000 kiosk \\
       && adduser -D -u 1000 -G kiosk -h /home/kiosk kiosk
   
   USER kiosk
   ENV DISPLAY=:0
   ENV XAUTHORITY=/home/kiosk/.Xauthority
   
   CMD ["chromium-browser", "--kiosk", "--start-fullscreen", "--app=https://player.yodeck.com"]

   Now build the container image:

   bash · build the image

   docker buildx build --platform=linux/arm64 -t yodeck-web-player:latest .

   This command compiles the container, making it ready for deployment on the ALPON.

2. 2

   Push the image to the Sixfab Container Registry

   Log in to Sixfab Registry, click + Add Container, and follow the prompts to push the image.

   Pushing images to the Sixfab Container Registry

   For the full walkthrough of tagging and pushing an image, see Update Containers from the Sixfab Container Registry.

3. 3

   Deploy the container on ALPON

   Before deploying, create a dedicated Xauthority file on the device for UID 1000, using the active display cookie. Open a shell on the device and run:

   bash · on the device · X11 authorization

   sudo install -m 0600 -o 1000 -g 1000 /dev/null /opt/yodeck.Xauthority
   sudo xauth -f /root/.Xauthority nlist :0 \\
     | sed -e 's/^..../ffff/' \\
     | sudo xauth -f /opt/yodeck.Xauthority nmerge -

   Then open your device in ALPON Cloud, go to the Applications section, and click + Deploy. In the Deploy Container window, use these settings:

   Container Name The application name, for example yodeck.

   Image The Yodeck Web Player image and immutable tag you pushed to the Sixfab Container Registry.

   Environment Click + Add More in the Environment section and add the key DISPLAY with the value :0.

   Volumes Click + Add More and add the two bind mounts in the table below, both read-only.

   Privileged Leave this off. The non-root user and Xauthority file give Chromium everything it needs.

   Access	Local Path	Target Path
   Read-only	/tmp/.X11-unix	/tmp/.X11-unix
   Read-only	/opt/yodeck.Xauthority	/home/kiosk/.Xauthority

   Click + Deploy to start the container.

4. 4

   Verify the player on the display

   Once the deployment is complete:

   1. Connect your ALPON X5 AI or ALPON X4 to a display.
   2. Restart the device if needed.
   3. The Yodeck Web Player launches automatically and shows the default Yodeck content.

   Now you can log into the Yodeck dashboard to manage the content remotely. From there, you can upload images, videos, or playlists, and your ALPON will update accordingly.