Commit 4a3717e6 authored by Adam Hawkins's avatar Adam Hawkins

Fix spelling errors

parent 27292e3f
......@@ -38,13 +38,13 @@ docker run --rm -it "${PWD}:/data" -w /data ruby:2.3 \
This mounts the current directory at `/data` then instructs the
container to write back to `/data`. Tada! This is how you can use a
container to generate artifcats on the Docker host.
container to generate artifacts on the Docker host.
## A Fix
This is the easiest to get data in/out of the container. This creates
a problem though since Docker containers are often run as root. This
approach may litter the filesystem with root owner artifacts depending
approach may litter the file system with root owner artifacts depending
on your Docker setup (e.g. the docker daemon runs directly on your
host or the docker daemon is running in a VM). The problem usually
reveals itself if the commands happen on CI. These machines usually
......@@ -70,7 +70,7 @@ work transparently.
## The Correct Way
There is a sure fire way to do this that works in 100% of scenarios
without any arounds. The solution is to use `docker cp`. The `cp`
without any workarounds. The solution is to use `docker cp`. The `cp`
command allows you to copy files into and out of containers. `cp`
works on individual files or directories. Files are copied directly
while directories are tarred. This solution requires a few more
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