### Summary Unable to delete container tags that have "missing manifest digest". The remove tag button is grey'ed out. More problematic is when attempting to delete the entire image repository, the repository is scheduled for deletion then after some time, the invalid container tags remain. These invalid tags cannot be deleted either one-by-one or by deleting the entire image repository. This has follow-on effects, like being unable to move the repository to another namespace. I would not like to delete and recreate the entire repository as a workaround. <!-- Summarize the bug encountered concisely. --> ### Steps to reproduce Create a Dockerfile. Build and push to Gitlab Registry using `docker buildx` ``` build-container: stage: build image: < use a base image with docker installed + buildx plugin installed > services: - docker:stable-dind script: - export IMAGE_BASE=$CI_REGISTRY_IMAGE - export IMAGE_CACHE_TAG=$CI_COMMIT_REF_NAME - echo $CI_REGISTRY_PASSWORD | docker login -u $CI_REGISTRY_USER $CI_REGISTRY --password-stdin - docker buildx create --use - docker buildx build --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHORT_SHA --tag $IMAGE_BASE:$IMAGE_CACHE_TAG --cache-from=type=registry,ref=$IMAGE_BASE:$IMAGE_CACHE_TAG --cache-to=type=registry,ref=$IMAGE_BASE:$IMAGE_CACHE_TAG --push . ``` 1. The image tags options are greyed out, there's no way to delete them. 2. Then try to delete the entire image repository 3. Expect that the entire image repository is deleted and no tags remain. Actually, tags remain. <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. --> ### Possible fixes The root cause for the UI issue you're seeing is https://gitlab.com/gitlab-org/gitlab/-/issues/232815. Regardless of the "invalid" message on the UI, nothing should stop us from deleting this tag through the UI/API. A tag delete request against the registry will definitely succeed. So I think we can do the following: 1. If a tag is deemed as invalid (for whatever reason), we should not gray out the delete option for that tag in the UI; 1. When deleting a tag (either through the UI or API), the backend (Rails) should not halt if unable to fetch/validate the underlying image manifest. It should handle such exceptions gracefully and call the container registry tag `delete` endpoint. ### Proposal This issue will focus on the backend work to ensure that when deleting a tag (either through the UI or API), the backend (Rails) should not halt if unable to fetch/validate the underlying image manifest. It should handle such exceptions gracefully and call the container registry tag `delete` endpoint. The follow-up issue, https://gitlab.com/gitlab-org/gitlab/-/issues/342866 will be scheduled once this issue is complete. ### Example Project Project ID: 21998547 <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### What is the current *bug* behavior? 1. The image tags options are greyed out, there's no way to delete them. 2. Then try to delete the entire image repository 3. Tags marked "missing manifest digest" remain. ### What is the expected *correct* behavior? 1. Be able to delete invalid tags from the interface. 1. Or be able to delete the entire image repository and no tags remain. ### Relevant logs and/or screenshots   ### Output of checks <!-- If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com --> #### Results of GitLab environment info Gitlab.com, GitLab Enterprise Edition 14.4.0-pre 4190ff47b10 <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details>