-
Notifications
You must be signed in to change notification settings - Fork 49
Description
Describe the bug
I'm running the following command to try to purge just untagged ACR images.
az acr run --registry myregistry--cmd "acr purge --filter 'myrepo:.*' --ago 300000d --untagged" /dev/nullThe ago is set so high so no tagged images are deleted based on the documentation here.
https://learn.microsoft.com/en-us/azure/container-registry/container-registry-auto-purge
Note
The --untagged filter doesn't respond to the --ago filter. For additional parameters, run acr purge --help.
This used to work, but at some point in the recent passed it stopped. My untagged image manifests are just piling up in the ACR causing me to be charged for storage that I don't need. There does not seem to be a way to simply purge untagged images anymore.
To Reproduce
Steps to reproduce the behavior:
- Run the command above with an ACR that has 1 tag and multiple untagged manifests.
- No manifests will be deleted
Number of tags to be deleted: 0
Number of manifests to be deleted: 0
2026/02/18 04:45:57 Successfully executed container: acb_step_0
2026/02/18 04:45:57 Step ID: acb_step_0 marked as successful (elapsed time in seconds: 0.850325)
Expected behavior
Untagged manifests should be deleted.
Screenshots
See output from the command run against and ACR with this showing in the portal
Any relevant environment information
- OS: Windows 11
- azure-cli 2.83.0
Additional context