M
MartinVyskocil

  • 12 minutes ago
  • Joined 12 Feb
  • 0 best answers
  • Hello,

    To the error:
    The error indicates that the identifier format in the oakapp.toml file is incorrect and does not follow the required format "com.app.example".
    Please double-check the identifier format in your oakapp.toml file.

    To the app installation:
    Yes, we are still working on the OAK4 tab, but the application doesn’t have to be installed only through the Hub—it can also be installed using oakctl.
    You can find the installation steps here:
    https://rvc4.docs.luxonis.com/software/tools/oakctl/#Usage-App%20Management-Install%20an%20app

    Best regards,
    Martin

  • Hello,

    You can check the documentation at https://rvc4.docs.luxonis.com/software/tools/oakctl/#oakapp.toml to learn how to create an oakapp that is supported on OAK4 devices and manageable via oakctl. You can create an oakapp from a Docker image, you just need to define this image in oakapp.toml using:

    [base_image]
    image_name = "library/debian"
    image_tag = "bookworm-slim"

    By default, it downloads images from Docker Hub, but you can specify a different repository. There are several limitations for the Docker image you can use: it must be a Debian 12-based image for ARM with Manifest V2. Alternatively, you can use a locally running registry and configure the [base_image] setting in oakapp.toml as follows:

    [base_image]
    api_url = "http://localhost:5000"
    image_name = "debian"
    image_tag = "bookworm-slim"

    Plus serve this on local network:

    podman run -d -p 5000:5000 --name registry registry:2.7
    
    npm install -g regctl
    wget <URL>/debian_bookworm-slim.tar
    
    regctl registry set --tls=disabled localhost:5000
    regctl image import localhost:5000/debian:bookworm-slim debian_bookworm-slim.tar

    Please let us know if the process was clear and led to the successful creation of an oakapp.
    We would appreciate any feedback or suggestions for improvement.

    Best regards,
    Martin

  • Hello,

    Accessing the deployed container – Currently, it is not possible to bash into the application, but this functionality will be available in the future.

    Docker images and persistent storage - We are not entirely sure what you're trying to achieve, as Docker is not available on OAK4. The device uses similar container technology through oakctl, but we would need more details to better understand your use case.

    Best regards,
    Martin

  • Hello,

    Thank you for reporting this issue.

    The upload functionality will be fixed in the next release, scheduled for Thursday.

    Regarding OAK4 device support in the Hub, we are actively working on it. In the meantime, these devices have been placed in a separate OAK4 section.

    Best regards,
    Martin