CVAT Administration
This knowledge base is for CVAT administrators. Last updated August 21, 2021.
Last updated
This knowledge base is for CVAT administrators. Last updated August 21, 2021.
Last updated
Log into AWS EC2 with AWS credentials, and select the CVAT server instance. Note that you should have superadmin access in CVAT to begin with if you are performing this step. First, follow the steps at the CVAT Github repo to get started.
After the initial build, you can restart the CVAT app with the following commands:
cd cvat
docker-compose -f docker-compose.yml -f components/analytics/docker-compose.analytics.yml -f docker-compose.override.yml build
docker-compose -f docker-compose.yml -f components/analytics/docker-compose.analytics.yml -f docker-compose.override.yml up -d
Note that this rebuilding step will not erase/modify existing annotations, users, tasks, etc.- these are persisted in the associated Docker volumes. To erase the app completely, you will need to delete all associated volumes as well.
Changes in the docker-compose.override.yaml file should follow a format similar to:
Known Issues and Bugs:
“Bind address in use” during docker-build
Solution: a service is blocking the port you are trying to use. sudo /etc/init.d/apache2 stop usually works.
This is applicable for anyone who has been added as a user in a deployed CVAT instance.
Clone thecvat repo and use ./cli.py in cvat/utils/cli/
Known Issues and Bugs:
Despite being marked as optional, “label” option is not optional and must be supplied when creating a new task:
Ex. you can use assignee:x AND status:validation to see what tasks from an individual need to be validated still.