cvat-ui

packaged by Chainguard

Chainguard Container for cvat-ui

CVAT is a leading data annotation platform for image, video, audio, and 3D datasets. It offers open-source, cloud, and enterprise products, as well as labeling services, with AI-assisted labeling, quality assurance, team collaboration, analytics, and developer APIs.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/cvat-ui:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard cvat-ui container image is designed to be a drop-in replacement for the upstream cvat/ui image. It serves the CVAT React/TypeScript single-page web application as static assets with nginx, and uses the same entrypoint (/docker-entrypoint.sh), command (nginx -g 'daemon off;'), and stop signal (SIGQUIT) as upstream. Like most Chainguard images, this container image is minimal and does not include unnecessary components such as a package manager.

This image runs as the non-root nginx user (UID and GID 101), matching upstream. Because the bundled nginx configuration has no listen directive, nginx listens on port 8000, which is the port the CVAT Helm chart and Docker Compose deployment expect for the frontend. The nginx PID file and temporary files are written under /tmp, and access and error logs go to stdout and stderr.

The CVAT UI and CVAT server are released in lockstep, so the cvat-ui image tag must match the version of the CVAT server you run alongside it. Chainguard tags have no v prefix: cgr.dev/ORGANIZATION/cvat-ui:2.80.0 corresponds to the upstream cvat/server:v2.80.0 image.

Getting Started

In the examples below, replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Running with Docker

docker run -d --name cvat-ui -p 8000:8000 cgr.dev/ORGANIZATION/cvat-ui:latest

Once running, the UI is available at http://localhost:8000. In a full CVAT deployment the UI is placed behind the CVAT reverse proxy alongside the CVAT server, which handles the /api routes.

Using with the CVAT Helm chart

The CVAT Helm chart deploys the frontend from the cvat.frontend.image and cvat.frontend.tag values. Check out the chart from a tagged CVAT release and pin the frontend and backend to that same release:

git clone --branch v2.80.0 https://github.com/cvat-ai/cvat
cd cvat
helm dependency update ./helm-chart
helm install cvat ./helm-chart \
  --set cvat.frontend.image=cgr.dev/ORGANIZATION/cvat-ui \
  --set cvat.frontend.tag=2.80.0 \
  --set cvat.backend.tag=v2.80.0

Replace 2.80.0 with the CVAT release you deploy, keeping the cvat-ui tag and the backend tag on the same version.

Configuration

The nginx site configuration lives at /etc/nginx/conf.d/default.conf and the static application at /usr/share/nginx/html. The /etc/nginx directory is owned by the nginx user, so the standard nginx entrypoint scripts in /docker-entrypoint.d can render templates mounted under /etc/nginx/templates at startup. Any configuration you mount must be readable by UID 101.

Documentation and Resources

• CVAT GitHub Repository
• CVAT Documentation

CVAT is licensed under the MIT License.

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.