Cleaning up full instance disk space
Written by
Updated at March 14, 2024
A GitLab instance can run out of disk space. This is indicated by the 500 Internal Server Error
HTTP status code. In this case, clean up the instance disk space and prevent future disk overflows.
Clean up the instance disk space
- Manually review
all Docker images and their tags in GitLab Container Registry. - Delete
outdated images and tags.
Prevent disk space overflow
To prevent your instance disk space from overflowing, use any of the following options:
- Set the expiration time for build artifacts
at the instance level. Its default value is 30 days. - Create and configure a tag cleanup policy
at the level of individual projects utilizing GitLab Container Registry. - If you are using a Yandex Container Registry integration, create and configure a Docker image cleanup policy for Yandex Container Registry.