Commit 8251c856 authored by Nourdin el Bacha's avatar Nourdin el Bacha

Improve grammar to dind workflow information

parent eb459b35
...@@ -114,9 +114,9 @@ Docker-in-Docker works well, and is the recommended configuration, but it is ...@@ -114,9 +114,9 @@ Docker-in-Docker works well, and is the recommended configuration, but it is
not without its own challenges: not without its own challenges:
- When using docker-in-docker, each job is in a clean environment without the past - 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 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 - 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) the recommended storage driver. See [Using the overlayfs driver](#using-the-overlayfs-driver)
for details. for details.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment