Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
8251c856
Commit
8251c856
authored
Mar 03, 2020
by
Nourdin el Bacha
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve grammar to dind workflow information
parent
eb459b35
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/ci/docker/using_docker_build.md
doc/ci/docker/using_docker_build.md
+2
-2
No files found.
doc/ci/docker/using_docker_build.md
View file @
8251c856
...
...
@@ -114,9 +114,9 @@ Docker-in-Docker works well, and is the recommended configuration, but it is
not without its own challenges:
-
When using docker-in-docker, each job is in a clean environment without the past
history. Concurrent jobs work fine because every build gets it
'
s own
history. Concurrent jobs work fine because every build gets its own
instance of Docker engine so they won't conflict with each other. But this
also means jobs can be slower because there's no caching of layers.
also means
that
jobs can be slower because there's no caching of layers.
-
By default, Docker 17.09 and higher uses
`--storage-driver overlay2`
which is
the recommended storage driver. See
[
Using the overlayfs driver
](
#using-the-overlayfs-driver
)
for details.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment