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-tasks-agent-pools.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Use dedicated pool to run task - Tasks
3
-
description: Use a dedicated compute pool (agent pool) to run an Azure Container Registry task.
3
+
description: Set up a dedicated compute pool (agent pool) in your registry to run an Azure Container Registry task.
4
4
ms.topic: article
5
5
ms.date: 04/30/2020
6
6
---
@@ -26,15 +26,14 @@ This feature is available in the **Premium** container registry service tier. Fo
26
26
27
27
- Task agent pools currently support Linux nodes. Windows nodes are not currently supported.
28
28
- Task agent pools are available in preview in the following regions: West US 2, South Central US, East US 2, and East US.
29
-
- For each registry, the default total vCPU (core) quota for all agent pools is 16. Please [open a support ticket][open-support-ticket] for additional allocation.
30
-
29
+
- For each registry, the default total vCPU (core) quota for all agent pools is 16. Open a support ticket][open-support-ticket] for additional allocation.
31
30
32
31
## Prerequisites
33
32
34
33
* To use the Azure CLI steps in this article, Azure CLI version 2.3.1 or later is required. If you need to install or upgrade, see [Install Azure CLI][azure-cli]. Or run in [Azure Cloud Shell](../cloud-shell/quickstart.md).
35
34
* If you don't already have a container registry, [create one][create-reg-cli](https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-azure-cli) (Premium tier required) in a preview region.
36
35
37
-
## Pool tiers
36
+
## Pool tiers
38
37
39
38
The following table shows the resources per instance in the agent pool tiers.
40
39
@@ -66,7 +65,7 @@ az acr agentpool create \
66
65
--tier S2
67
66
```
68
67
69
-
Creating an agent pool and other pool operations can take several minutes to complete.
68
+
Creating an agent pool and other pool management operations will take several minutes to complete.
70
69
71
70
### Scale pool
72
71
@@ -99,7 +98,8 @@ Task agent pools require access to the following Azure services. The following f
99
98
The following example creates an agent pool in the *mysubnet* subnet of network *myvnet*:
100
99
101
100
```azurecli
102
-
subnet=$(az network vnet subnet show \
101
+
# Get the subnet ID
102
+
subnetId=$(az network vnet subnet show \
103
103
--resource-grop myresourcegroup \
104
104
--vnet-name myvnet \
105
105
--name mysubnetname \
@@ -108,15 +108,15 @@ subnet=$(az network vnet subnet show \
108
108
az acr agentpool create \
109
109
--name myagentpool \
110
110
--tier S2 \
111
-
--subnet-id $subnet
111
+
--subnet-id $subnetId
112
112
```
113
113
114
-
## Run tasks on agent pool
114
+
## Run task on agent pool
115
115
116
-
The following sections show how to specify an agent pool when queuing a task.
116
+
The following examples show how to specify an agent pool when queuing a task.
117
117
118
118
> [!NOTE]
119
-
> To use an agent pool in an ACR Task, ensure that the pool contains at least 1 instance.
119
+
> To use an agent pool in an ACR task, ensure that the pool contains at least 1 instance.
120
120
>
121
121
122
122
### Quick task run
@@ -133,7 +133,7 @@ az acr build \
133
133
134
134
### Automatically triggered task
135
135
136
-
For example, create a scheduled task on the agent pool with [az acr task create][az-acr-task-create].
136
+
For example, create a scheduled task on the agent pool with [az acr task create][az-acr-task-create], passing the `--agent-pool` parameter.
137
137
138
138
```azurecli
139
139
az acr task create \
@@ -155,7 +155,7 @@ az acr task run \
155
155
156
156
### Query pool status
157
157
158
-
Query the agent pool queue status (current scheduled runs on the agent pool) by running [az acr agentpool show][az-acr-agentpool-show].
158
+
Query the agent pool queue status (the number of runs currently scheduled on the agent pool) by running [az acr agentpool show][az-acr-agentpool-show].
Copy file name to clipboardExpand all lines: articles/container-registry/container-registry-vnet.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ If instead you need to set up access rules for resources to reach a container re
24
24
25
25
* Only an [Azure Kubernetes Service](../aks/intro-kubernetes.md) cluster or Azure [virtual machine](../virtual-machines/linux/overview.md) can be used as a host to access a container registry in a virtual network. *Other Azure services including Azure Container Instances aren't currently supported.*
26
26
27
-
*[ACR Tasks](container-registry-tasks-overview.md)operations aren't currently supported in a container registry accessed in a virtual network.
27
+
*Running [ACR Tasks](container-registry-tasks-overview.md) in a container registry accessed in a virtual network requires a [dedicated agent pool](container-registry-tasks-agent-pools.md).
28
28
29
29
* Each registry supports a maximum of 100 virtual network rules.
0 commit comments