Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
gitlab-runner
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
GitLab.org
gitlab-runner
Commits
356a680e
Verified
Commit
356a680e
authored
5 years ago
by
Achilleas Pipinellis
Browse files
Options
Downloads
Patches
Plain Diff
Fix typo in Docker executors doc
parent
83323c12
No related branches found
No related tags found
Loading
Pipeline
#56856397
passed
5 years ago
Stage: prebuild
Stage: test
Stage: cleanup
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/executors/docker.md
+11
-10
11 additions, 10 deletions
docs/executors/docker.md
with
11 additions
and
10 deletions
docs/executors/docker.md
+
11
−
10
View file @
356a680e
# The Docker executor
GitLab Runner can use Docker to run
build
s on user provided images. This is
GitLab Runner can use Docker to run
job
s on user provided images. This is
possible with the use of
**Docker**
executor.
The
**Docker**
executor when used with GitLab CI, connects to [Docker Engine]
...
...
@@ -22,18 +22,19 @@ compatible versions of Docker.
## Workflow
The Docker executor divides the
build
into multiple steps:
The Docker executor divides the
job
into multiple steps:
1.
**Prepare**
: Create and start the services.
1.
**Pre-build**
: Clone, restore cache and download artifacts from previous
stages. This is run on a special Docker Image.
1.
**Build**
: User build. This is run on the user-provided docker image.
1.
**Post-build**
: Create cache, upload artifacts to GitLab. This is run on
1.
**Prepare**
: Create and start the
[
services
](
https://docs.gitlab.com/ee/ci/yaml/#services
)
.
1.
**Pre-job**
: Clone, restore
[
cache
](
https://docs.gitlab.com/ee/ci/yaml/#cache
)
and download
[
artifacts
](
https://docs.gitlab.com/ee/ci/yaml/#artifacts
)
from previous
stages. This is run on a special Docker image.
1.
**Job**
: User build. This is run on the user-provided Docker image.
1.
**Post-job**
: Create cache, upload artifacts to GitLab. This is run on
a special Docker Image.
The special Docker
I
mage is based on [Alpine Linux] and contains all the tools
required to run the prepare
step the build: the Git binary and the Runner
binar
y
for supporting caching and artifacts. You can find the definition of
The special Docker
i
mage is based on [Alpine Linux] and contains all the tools
required to run the prepare
, pre-job, and post-job steps, like the Git and the
Runner
binar
ies
for supporting caching and artifacts. You can find the definition of
this special image
[
in the official Runner repository
][
special-build
]
.
## The `image` keyword
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment