Images from the private Container Registry getting deleted even with 'Cleanup Disabled'

GitLab CI/CD
, ,
1

Summary

Images that are being published to the Container Registry (private) are getting automatically deleted even though the ‘Cleanup disabed’ flag is active. Notes:

-The usage/storage quota of the project has not been exhausted. (0 extra storage)

-Only one instance of this behaviour has been observed.

Steps to reproduce

  • Publish an image to GitLab’s container registry via GitLab CI.

What is the current bug behavior?

Images that are being published to the Container Registry (private) are getting automatically deleted even though the ‘Cleanup disabed’ flag is active.

Notes:

-The usage/storage quota of the project has not been exhausted. (0 extra storage)

-Only one instance of this behaviour has been observed.

What is the expected correct behavior?

All images should be preserved in the Container Registry when Cleanup is disabled.

Relevant logs and/or screenshots

issue

Output of checks

This bug happens on GitLab.com

Is there any way to track if someone has deleted a container from a private registry?
Any logs/stack traces that can help in determining the state of the registries before deletions.

Thanks

2

There is the Audit feature in Premium and higher tier. If you are on the Free tier there is no way to find out if someone deleted image from registry.