Azure-docs: Missing any documentation on the quota

Created on 10 May 2018  Â·  6Comments  Â·  Source: MicrosoftDocs/azure-docs

Please add an explanation for how the quota works. I'm not finding any information on this. I have an ACR that just has 1 image that is replaced daily with an updated copy yet my quota ran out. It would be nice to understand why.


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

assigned-to-author container-registrsvc doc-enhancement triaged

Most helpful comment

@novaterata I've got a work item currently in the queue for a Troubleshooting doc, and this would be a good fit for that. As well, I could add a note the Image storage article that contains a small section on gotchas such as this one.

@MicahMcKittrick-MSFT, you can go ahead and assign this one to me, and I'll get it in the work queue.

All 6 comments

@novaterata I am not seeing any limits for images stored:

image

However depending on which SKU you picked you get different amount of storage:
image

Do you know which SKU you are using?

The issue I'm having was that dangling images were taking up all my
storage, but this invisible in the UI as untagged images aren't listed.
Some explanation about the Quota would be good, because it made no sense
until I figured that out

On Thu, May 10, 2018, 1:05 PM Micah notifications@github.com wrote:

@novaterata https://github.com/novaterata I am not seeing any limits
for images stored:

[image: image]
https://user-images.githubusercontent.com/32313503/39882762-974201a8-5439-11e8-9ff7-fc461ddefb83.png

However depending on which SKU you picked you get different amount of
storage:
[image: image]
https://user-images.githubusercontent.com/32313503/39882782-a6aa503c-5439-11e8-9af6-621bd2ec4d34.png

Do you know which SKU you are using?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/8392#issuecomment-388118165,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABlGHZvPzk_xo0fwzTC658w45VcMrPy9ks5txHNvgaJpZM4T50gP
.

@novaterata I've got a work item currently in the queue for a Troubleshooting doc, and this would be a good fit for that. As well, I could add a note the Image storage article that contains a small section on gotchas such as this one.

@MicahMcKittrick-MSFT, you can go ahead and assign this one to me, and I'll get it in the work queue.

Thanks, I'm all good now, but it was a real mystery for awhile

On Thu, May 10, 2018, 2:55 PM Marsh Macy notifications@github.com wrote:

@novaterata https://github.com/novaterata I've got a work item
currently in the queue for a Troubleshooting doc, and this would be a good
fit for that. As well, I could add a note the Image storage
https://docs.microsoft.com/en-us/azure/container-registry/container-registry-storage
article that contains a small section on gotchas such as this one.

@MicahMcKittrick-MSFT https://github.com/MicahMcKittrick-MSFT, you can
go ahead and assign this one to me, and I'll get it in the work queue.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/8392#issuecomment-388150847,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABlGHUh7PyQSgK2dO2GRRV6OOjeW38Jxks5txI01gaJpZM4T50gP
.

@MicahMcKittrick-MSFT Let's go ahead and close this one. I've captured this request in a work item and anticipate addressing in the current or following sprint.

Internal tracking: User Story 1140386

please-close

@novaterata We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Was this page helpful?
0 / 5 - 0 ratings