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: docs/pipelines/process/container-phases.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ For a container job, the agent first fetches and starts the container, and then
30
30
Linux-based containers also have the following requirements:
31
31
32
32
- Bash installed.
33
-
- GNU C Library (glibc)-based. Non-glibc containers require added setup. For more information, see [Nonglibc-based containers](#nonglibc-based-containers).
33
+
- GNU C Library (`glibc`)-based. Nonglibc containers require added setup. For more information, see [Nonglibc-based containers](#nonglibc-based-containers).
34
34
- No `ENTRYPOINT`. Containers with an `ENTRYPOINT` might not work, because [docker exec](https://docs.docker.com/reference/cli/docker/container/exec) expects the container to always be running.
35
35
-`USER` provided with access to `groupadd` and other privileged commands without using `sudo`.
36
36
- Ability to run Node.js, which the agent provides.
@@ -112,7 +112,7 @@ steps:
112
112
113
113
A container job uses the underlying host agent's Docker configuration file for image registry authorization. This file signs out at the end of the Docker registry container initialization.
114
114
115
-
Registry image pulls for container jobs could be denied for `unauthorized authentication` if another job running in parallel on the agent already signed out the Docker configuration file. The solution is to set a Docker environment variable called `DOCKER_CONFIG` for each agent pool running on the hosted agent.
115
+
Registry image pulls for container jobs could be denied for unauthorized authentication if another job running in parallel on the agent already signed out the Docker configuration file. The solution is to set a Docker environment variable called `DOCKER_CONFIG` for each agent pool running on the hosted agent.
116
116
117
117
Export the `DOCKER_CONFIG` in each agent pool's *runsvc.sh* script as follows:
118
118
@@ -199,7 +199,7 @@ container:
199
199
200
200
## Nonglibc-based containers
201
201
202
-
The hosted Azure Pipelines agents supply Node.js, which is required to run tasks and scripts. The Node.js version compiles against the C runtime used in the hosted cloud, typically glibc. Some Linux variants use other C runtimes. For instance, Alpine Linux uses musl. For more information, see [Microsoft-hosted agents](../agents/hosted.md#software).
202
+
The hosted Azure Pipelines agents supply Node.js, which is required to run tasks and scripts. The Node.js version compiles against the C runtime used in the hosted cloud, typically `glibc`. Some Linux variants use other C runtimes. For instance, Alpine Linux uses `musl`. For more information, see [Microsoft-hosted agents](../agents/hosted.md#software).
203
203
204
204
If you want to use a nonglibc-based container in a pipeline, you must:
0 commit comments