Uploading Video File Error via VIA GUI

Accelerated Computing Intelligent Video Analytics Visual AI Agent
,
1

I’ve attempted to run the VIA engine inside k8s cluster. It’s ok to run the application in the Pod via the following yaml file.

apiVersion: v1
kind: Pod
metadata:
  name: via-engine
spec:
  containers:
  - name: via-engine
    image: nvcr.io/metropolis/via-dp/via-engine:2.0-dp
    resources:
      limits:
        nvidia.com/gpu: 1
      requests:
        nvidia.com/gpu: 1
    ports:
    - containerPort: 8000
      name: backend-port
    - containerPort: 9000
      name: frontend-port
    env:
    - name: BACKEND_PORT
      value: "8000"
    - name: FRONTEND_PORT
      value: "9000"
    - name: NVIDIA_API_KEY
      value: "<NVIDIA_API_KEY>"
    - name: NGC_API_KEY
      value: "<NGC_API_KEY>"
    - name: VLM_MODEL_TO_USE
      value: "vita-2.0"
    - name: MODEL_PATH
      value: "ngc:nvidia/tao/vita:2.0.1"
  restartPolicy: Never

It’s ok to load the GUI.

But when upload a small video file from GUI, it will just stuck there.

image
image2844×1108 291 KB

Then I’ve directly uploaded the video file via VIA’s backend API. It’s fine.

Not sure where is the problem in VIA engine, the network? or any permission? Seems like it’s a frontend issue.

2

image
image2430×950 157 KB

If just using backend api, it’s fine.

3

In theory, there should be no restrictions on uploading files. Have you tried running with our docker command directly without k8s?

Also how your service is exposed and could you try to set the hostPort in your config file like below?

    ports:
    - containerPort: 8000
      name: backend-port
    - containerPort: 9000
      name: frontend-port
      hostPort: 10018
6

Hi @cyrus.cao , has this problem been solved by the method we provided?

7

The issue has been solved. I’ve tried it on docker, it works well. Then I noticed there is a queue and event stream in this VIA application, which may need longer timeout limit. I’ve updated the setting in the K8s ingress, then it works in k8s as same as it was running in docker.

1 Like
8

Glad to hear that. Could you attach the new config file for others to refer to? Thanks in advance.

9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.