You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-registry/container-registry-faq.md
+16-10Lines changed: 16 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Frequently asked questions
3
3
description: Answers for frequently asked questions related to the Azure Container Registry service
4
4
author: sajayantony
5
5
ms.topic: article
6
-
ms.date: 07/02/2019
6
+
ms.date: 03/18/2020
7
7
ms.author: sajaya
8
8
---
9
9
@@ -99,7 +99,8 @@ It takes some time to propagate firewall rule changes. After you change firewall
99
99
-[How to enable TLS 1.2?](#how-to-enable-tls-12)
100
100
-[Does Azure Container Registry support Content Trust?](#does-azure-container-registry-support-content-trust)
101
101
-[How do I grant access to pull or push images without permission to manage the registry resource?](#how-do-i-grant-access-to-pull-or-push-images-without-permission-to-manage-the-registry-resource)
102
-
-[How do I enable automatic image quarantine for a registry](#how-do-i-enable-automatic-image-quarantine-for-a-registry)
102
+
-[How do I enable automatic image quarantine for a registry?](#how-do-i-enable-automatic-image-quarantine-for-a-registry)
103
+
-[How do I enable anonymous pull access?](#how-do-i-enable-anonymous-pull-access)
103
104
104
105
### How do I access Docker Registry HTTP API V2?
105
106
@@ -247,13 +248,18 @@ With the use of only the `AcrPull` or `AcrPush` role, the assignee doesn't have
247
248
248
249
Image quarantine is currently a preview feature of ACR. You can enable the quarantine mode of a registry so that only those images which have successfully passed security scan are visible to normal users. For details, see the [ACR GitHub repo](https://github.com/Azure/acr/tree/master/docs/preview/quarantine).
249
250
251
+
### How do I enable anonymous pull access?
252
+
253
+
Setting up an Azure container registry for anonymous (public) pull access is currently a preview feature. To enable public access, please open a support ticket at https://aka.ms/acr/support/create-ticket. For details, see the [Azure Feedback Forum](https://feedback.azure.com/forums/903958-azure-container-registry/suggestions/32517127-enable-anonymous-access-to-registries).
254
+
255
+
250
256
## Diagnostics and health checks
251
257
252
258
-[Check health with `az acr check-health`](#check-health-with-az-acr-check-health)
253
259
-[docker pull fails with error: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)](#docker-pull-fails-with-error-nethttp-request-canceled-while-waiting-for-connection-clienttimeout-exceeded-while-awaiting-headers)
254
260
-[docker push succeeds but docker pull fails with error: unauthorized: authentication required](#docker-push-succeeds-but-docker-pull-fails-with-error-unauthorized-authentication-required)
255
261
-[`az acr login` succeeds, but docker commands fails with error: unauthorized: authentication required](#az-acr-login-succeeds-but-docker-fails-with-error-unauthorized-authentication-required)
256
-
-[Enable and get the debug logs of the docker daemon](#enable-and-get-the-debug-logs-of-the-docker-daemon)
262
+
-[Enable and get the debug logs of the docker daemon](#enable-and-get-the-debug-logs-of-the-docker-daemon)
257
263
-[New user permissions may not be effective immediately after updating](#new-user-permissions-may-not-be-effective-immediately-after-updating)
258
264
-[Authentication information is not given in the correct format on direct REST API calls](#authentication-information-is-not-given-in-the-correct-format-on-direct-rest-api-calls)
259
265
-[Why does the Azure portal not list all my repositories or tags?](#why-does-the-azure-portal-not-list-all-my-repositories-or-tags)
@@ -319,13 +325,13 @@ Details of `--signature-verification` can be found by running `man dockerd`.
319
325
320
326
Make sure you use an all lowercase server URL, for example, `docker push myregistry.azurecr.io/myimage:latest`, even if the registry resource name is uppercase or mixed case, like `myRegistry`.
321
327
322
-
### Enable and get the debug logs of the Docker daemon
328
+
### Enable and get the debug logs of the Docker daemon
323
329
324
330
Start `dockerd` with the `debug` option. First, create the Docker daemon configuration file (`/etc/docker/daemon.json`) if it doesn't exist, and add the `debug` option:
325
331
326
332
```json
327
-
{
328
-
"debug": true
333
+
{
334
+
"debug": true
329
335
}
330
336
```
331
337
@@ -335,12 +341,12 @@ Then, restart the daemon. For example, with Ubuntu 14.04:
335
341
sudo service docker restart
336
342
```
337
343
338
-
Details can be found in the [Docker documentation](https://docs.docker.com/engine/admin/#enable-debugging).
344
+
Details can be found in the [Docker documentation](https://docs.docker.com/engine/admin/#enable-debugging).
339
345
340
-
* The logs may be generated at different locations, depending on your system. For example, for Ubuntu 14.04, it's `/var/log/upstart/docker.log`.
341
-
See [Docker documentation](https://docs.docker.com/engine/admin/#read-the-logs) for details.
346
+
* The logs may be generated at different locations, depending on your system. For example, for Ubuntu 14.04, it's `/var/log/upstart/docker.log`.
347
+
See [Docker documentation](https://docs.docker.com/engine/admin/#read-the-logs) for details.
342
348
343
-
* For Docker for Windows, the logs are generated under %LOCALAPPDATA%/docker/. However it may not contain all the debug information yet.
349
+
* For Docker for Windows, the logs are generated under %LOCALAPPDATA%/docker/. However it may not contain all the debug information yet.
344
350
345
351
In order to access the full daemon log, you may need some extra steps:
Copy file name to clipboardExpand all lines: articles/container-registry/container-registry-repository-scoped-permissions.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,7 @@ Scenarios for creating a token include:
22
22
23
23
* This feature is only available in a **Premium** container registry. For information about registry service tiers and limits, see [Azure Container Registry SKUs](container-registry-skus.md).
24
24
* You can't currently assign repository-scoped permissions to an Azure Active Directory identity, such as a service principal or managed identity.
25
+
* You can't create a scope map in a registry enabled for [anonymous pull access](container-registry-faq.md#how-do-i-enable-anonymous-pull-access).
0 commit comments