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.yml
+18-13Lines changed: 18 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ sections:
38
38
How do I get admin credentials for a container registry?
39
39
answer: |
40
40
> [!IMPORTANT]
41
-
> The admin user account is designed for a single user to access the registry, mainly for testing purposes. We do not recommend sharing the admin account credentials with multiple users. Individual identity is recommended for users and service principals for headless scenarios. See [Authentication overview](container-registry-authentication.md).
41
+
> The admin user account is designed for a single user to access the registry, mainly for testing purposes. We don't recommend sharing the admin account credentials with multiple users. Individual identity is recommended for users and service principals for headless scenarios. See [Authentication overview](container-registry-authentication.md).
42
42
43
43
Before getting admin credentials, make sure the registry's admin user is enabled.
44
44
@@ -58,7 +58,7 @@ sections:
58
58
How do I get admin credentials in a Resource Manager template?
59
59
answer: |
60
60
> [!IMPORTANT]
61
-
> The admin user account is designed for a single user to access the registry, mainly for testing purposes. We do not recommend sharing the admin account credentials with multiple users. Individual identity is recommended for users and service principals for headless scenarios. See [Authentication overview](container-registry-authentication.md).
61
+
> The admin user account is designed for a single user to access the registry, mainly for testing purposes. We don't recommend sharing the admin account credentials with multiple users. Individual identity is recommended for users and service principals for headless scenarios. See [Authentication overview](container-registry-authentication.md).
62
62
63
63
Before getting admin credentials, make sure the registry's admin user is enabled.
64
64
@@ -89,7 +89,7 @@ sections:
89
89
```
90
90
91
91
- question: |
92
-
Firewall rules are updated successfully but they do not take effect
92
+
Firewall rules are updated successfully but they don't take effect
93
93
answer: |
94
94
It takes some time to propagate firewall rule changes. After you change firewall settings, please wait for a few minutes before verifying this change.
95
95
@@ -103,7 +103,7 @@ sections:
103
103
104
104
105
105
- question: |
106
-
How do I delete all manifests that are not referenced by any tag in a repository?
106
+
How do I delete all manifests that aren't referenced by any tag in a repository?
107
107
answer: |
108
108
If you are on bash:
109
109
@@ -130,7 +130,7 @@ sections:
130
130
- question: |
131
131
How do I validate storage quota changes?
132
132
answer: |
133
-
Create an image with a 1GB layer using the following docker file. This ensures that the image has a layer that is not shared by any other image in the registry.
133
+
Create an image with a 1GB layer using the following docker file. This ensures that the image has a layer that isn't shared by any other image in the registry.
134
134
135
135
```dockerfile
136
136
FROM alpine
@@ -199,7 +199,7 @@ sections:
199
199
* Public keys and certificates of all roles (except delegation roles) are stored in the `root.json`.
200
200
* Public keys and certificates of the delegation role are stored in the JSON file of its parent role (for example `targets.json` for the `targets/releases` role).
201
201
202
-
It is suggested to verify those public keys and certificates after the overall TUF verification done by the Docker and Notary client.
202
+
It's suggested to verify those public keys and certificates after the overall TUF verification done by the Docker and Notary client.
203
203
204
204
- question: |
205
205
How do I grant access to pull or push images without permission to manage the registry resource?
@@ -307,12 +307,12 @@ sections:
307
307
- question: |
308
308
Docker pull is slow
309
309
answer: |
310
-
Use [this](http://www.azurespeed.com/Azure/Download) tool to test your machine network download speed. If machine network is slow, consider using Azure VM in the same region as your registry. This usually gives you faster network speed.
310
+
Use [the speed tool](http://www.azurespeed.com/Azure/Download) to test your machine network download speed. If machine network is slow, consider using Azure VM in the same region as your registry to improve network speed.
311
311
312
312
- question: |
313
313
Docker push is slow
314
314
answer: |
315
-
Use [this](http://www.azurespeed.com/Azure/Upload) tool to test your machine network upload speed. If machine network is slow, consider using Azure VM in the same region as your registry. This usually gives you faster network speed.
315
+
Use [the speed tool](http://www.azurespeed.com/Azure/Upload) to test your machine network upload speed. If machine network is slow, consider using Azure VM in the same region as your registry to improve network speed.
316
316
317
317
- question: |
318
318
Docker push succeeds but docker pull fails with error: unauthorized: authentication required
@@ -392,7 +392,7 @@ sections:
392
392
When you grant new permissions (new roles) to a service principal, the change might not take effect immediately. There are two possible reasons:
393
393
394
394
* Azure Active Directory role assignment delay. Normally it's fast, but it could take minutes due to propagation delay.
395
-
* Permission delay on ACR token server. This could take up to 10 minutes. To mitigate, you can `docker logout` and then authenticate again with the same user after 1 minute:
395
+
* Permission delay on ACR token server could take up to 10 minutes. To mitigate, you can `docker logout` and then authenticate again with the same user after 1 minute:
396
396
397
397
```bash
398
398
docker logout myregistry.azurecr.io
@@ -416,7 +416,7 @@ sections:
416
416
```
417
417
418
418
- question: |
419
-
Authentication information is not given in the correct format on direct REST API calls
419
+
Authentication information isn't given in the correct format on direct REST API calls
420
420
answer: |
421
421
You may encounter an `InvalidAuthenticationInfo` error, especially using the `curl` tool with the option `-L`, `--location` (to follow redirects).
422
422
For example, fetching the blob using `curl` with `-L` option and basic authentication:
@@ -446,7 +446,7 @@ sections:
446
446
- question: |
447
447
Why does the Azure portal not list all my repositories or tags?
448
448
answer: |
449
-
If you are using the Microsoft Edge/IE browser, you can see at most 100 repositories or tags. If your registry has more than 100 repositories or tags, we recommend that you use either the Firefox or Chrome browser to list them all.
449
+
If you're using the Microsoft Edge/IE browser, you can see at most 100 repositories or tags. If your registry has more than 100 repositories or tags, we recommend that you use either the Firefox or Chrome browser to list them all.
450
450
451
451
- question: |
452
452
Why does the Azure portal fail to fetch repositories or tags?
@@ -524,7 +524,7 @@ sections:
524
524
- question: |
525
525
Does Tasks support GitLab for Source triggers?
526
526
answer: |
527
-
We currently do not support GitLab for Source triggers.
527
+
We currently don't support GitLab for Source triggers.
528
528
529
529
- question: |
530
530
What git repository management service does Tasks support?
How to resolve if the Agent pool creation fails due to timeout issues?
552
+
answer: |
553
+
Set up the correct [firewalls rules](/azure/container-registry/tasks-agent-pools#add-firewall-rules) to the existing network security groups or user-defined routes. After the setup, wait a few minutes for the firewall rules to apply.
0 commit comments