Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix description of commands that create new layers #97

Merged
merged 1 commit into from
Aug 27, 2019
Merged

Fix description of commands that create new layers #97

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Fix description of commands that create new layers 
Only RUN, COPY and ADD actually create new layers, so I improved the text to reflect this.
  • Loading branch information
@JKrag
JKrag authored Aug 27, 2019
commit 81aa11eb7f0fd7ae0016a9e98f701c589803dd02
2 changes: 1 addition & 1 deletion labs/07-building-an-image.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -263,7 +263,7 @@ Head over to `http://localhost:8888` or your server's URL and your app should be

## and layers

When dealing with docker images, a layer, or image layer is a change on an image, or an intermediate image. Every command you specify (FROM, RUN, COPY, etc.) in your Dockerfile causes the previous image to change, thus creating a new layer. You can think of it as staging changes when you're using Git: You add a file's change, then another one, then another one...
When dealing with docker images, a layer, or image layer is a change on an image, or an intermediate image. Every time you run one of the commands RUN, COPY or ADD in your Dockerfile it causes the previous image to change, thus creating a new layer. You can think of it as staging changes when you're using Git: You add a file's change, then another one, then another one...

Consider the following Dockerfile:

Expand Down