Creating a Kbox Image

Before creating a video stream cloud phone image, create a Kbox image first.

1. Obtain the Kbox container startup dependency components android.tar and Kbox-AOSP15.zip based on Deploying the Basic Environment for the Kbox Container, and upload them to the /home/kbox_video directory on the server. (This directory is used as an example. You can customize a directory as required.)
2. Decompress the Kbox-AOSP15.zip package, extract the android_kbox_aosp15.sh and base_box_aosp15.sh files in the deploy_scripts directory to the /home/kbox_video directory, and grant permissions on the files. Ensure that the file owner has the read, write, and execute permissions while users in the owner group and other users have only the read and execute permissions.

   1 2 3 4 5

   unzip Kbox-AOSP15.zip cp Kbox-AOSP15/deploy_scripts/base_box_aosp15.sh /home/kbox_video/ cp Kbox-AOSP15/deploy_scripts/android_kbox_aosp15.sh /home/kbox_video/ chmod 755 /home/kbox_video/base_box_aosp15.sh chmod 755 /home/kbox_video/android_kbox_aosp15.sh

3. Create a Kbox image named kbox:origin.
   1. Upload the Kbox demo image package android.tar to the ~/dependency directory (this directory is only an example and can be customized) and mount the image package.

      You can customize the image name and tag in the format of {Name}:{Tag}. In this example, the image name is kbox:demo.

      1 2	cd ~/dependency docker import android.tar kbox:demo

   2. Upload the deploy_scripts directory in the Kbox-AOSP15 folder to the ~/dependency directory on the server.
   3. Upload the Android Kbox binary file package BoostKit-boostcph-kbox_*.zip to ~/dependency/deploy_scripts.
   4. (Hardware configuration scheme 2/3) If hardware configuration scheme 2/3 is used, decompress the GPU driver package VAGPU-25.03.01.01-RC13-A15.tgz to obtain va_driver.tgz and upload va_driver.tgz to the ~/dependency/deploy_scripts directory on the server.
   5. Create a Kbox image that contains the Android Kbox binary. In the following commands, kbox:demo is the official Kbox demo image, and kbox:origin is the new image that contains the Android Kbox binary.
      • For configuration scheme 1:

        1 2 3

        cd ~/dependency/deploy_scripts chmod +x make_image_aosp15.sh ./make_image_aosp15.sh kbox:demo kbox:origin

      • For configuration scheme 2/3:

        1 2 3

        cd ~/dependency/deploy_scripts chmod +x make_image_aosp15.sh ./make_image_aosp15.sh kbox:demo kbox:origin va_driver.tgz

        

        After step 3 is performed, multiple alarms related to linker configuration are displayed in the command output. The alarms do not affect normal functionality and can be ignored.

        

4. Check whether the Kbox image (kbox:origin) is successfully created.

   1	docker images

   If the following information is displayed, the image is successfully created:

   1 2	REPOSITORY TAG IMAGE ID CREATED SIZE kbox origin d1f5cfd2e722 6 seconds ago 2.09GB