Skip to content

Commit e0a4c1f

Browse files
authored
Merge pull request #196773 from tejaswikolli-web/USERSTORY12413659
USER STORY 12413659
2 parents d40984a + f93a7e8 commit e0a4c1f

File tree

1 file changed

+18
-13
lines changed

1 file changed

+18
-13
lines changed

articles/container-registry/container-registry-faq.yml

Lines changed: 18 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ sections:
3838
How do I get admin credentials for a container registry?
3939
answer: |
4040
> [!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).
4242
4343
Before getting admin credentials, make sure the registry's admin user is enabled.
4444
@@ -58,7 +58,7 @@ sections:
5858
How do I get admin credentials in a Resource Manager template?
5959
answer: |
6060
> [!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).
6262
6363
Before getting admin credentials, make sure the registry's admin user is enabled.
6464
@@ -89,7 +89,7 @@ sections:
8989
```
9090
9191
- 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
9393
answer: |
9494
It takes some time to propagate firewall rule changes. After you change firewall settings, please wait for a few minutes before verifying this change.
9595
@@ -103,7 +103,7 @@ sections:
103103
104104
105105
- 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?
107107
answer: |
108108
If you are on bash:
109109
@@ -130,7 +130,7 @@ sections:
130130
- question: |
131131
How do I validate storage quota changes?
132132
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.
134134
135135
```dockerfile
136136
FROM alpine
@@ -199,7 +199,7 @@ sections:
199199
* Public keys and certificates of all roles (except delegation roles) are stored in the `root.json`.
200200
* 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).
201201
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.
203203
204204
- question: |
205205
How do I grant access to pull or push images without permission to manage the registry resource?
@@ -307,12 +307,12 @@ sections:
307307
- question: |
308308
Docker pull is slow
309309
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.
311311
312312
- question: |
313313
Docker push is slow
314314
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.
316316
317317
- question: |
318318
Docker push succeeds but docker pull fails with error: unauthorized: authentication required
@@ -392,7 +392,7 @@ sections:
392392
When you grant new permissions (new roles) to a service principal, the change might not take effect immediately. There are two possible reasons:
393393
394394
* 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:
396396
397397
```bash
398398
docker logout myregistry.azurecr.io
@@ -416,7 +416,7 @@ sections:
416416
```
417417
418418
- 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
420420
answer: |
421421
You may encounter an `InvalidAuthenticationInfo` error, especially using the `curl` tool with the option `-L`, `--location` (to follow redirects).
422422
For example, fetching the blob using `curl` with `-L` option and basic authentication:
@@ -446,7 +446,7 @@ sections:
446446
- question: |
447447
Why does the Azure portal not list all my repositories or tags?
448448
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.
450450
451451
- question: |
452452
Why does the Azure portal fail to fetch repositories or tags?
@@ -524,7 +524,7 @@ sections:
524524
- question: |
525525
Does Tasks support GitLab for Source triggers?
526526
answer: |
527-
We currently do not support GitLab for Source triggers.
527+
We currently don't support GitLab for Source triggers.
528528
529529
- question: |
530530
What git repository management service does Tasks support?
@@ -546,7 +546,12 @@ sections:
546546
547547
- [CircleCI](https://github.com/Azure/acr/blob/master/docs/integration/CircleCI.md)
548548
- [GitHub Actions](https://github.com/Azure/acr/blob/master/docs/integration/github-actions/github-actions.md)
549-
549+
550+
- question: |
551+
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.
554+
550555
additionalContent: |
551556
552557
## Next steps

0 commit comments

Comments
 (0)