What files are the .dockerignore work on?
I don’t really understand
Is it means like the fllow:
First I add somethings in it such as
- set docker container env from daemon configuration file
- After building a docker image how can I run the image without pushing to docker hub?
- How to Setup a Docker Tomcat Container on Mac OS X
- Run installation command in an already existing docker image (not container)?
- WSO2 loss APIs after changes in docker container
- Kubernetes Docker OS parameters vs Host OS parameters
Then I put this
After that I run a container and enter this container.
I make a new file named
test.mdand commit this container to new image
The new image will ignore this file so it will not in new container.
3 Solutions collect form web for “What files are the .dockerignore work on?”
Before explaining the use of the .dockerignore file we must spend a little time understanding what
docker build do.
Docker build. What does happen when I build an image ?
When you build an image from a Dockerfile using the
docker build command the daemon will create a context. That context contain everything in the directory you executed the command in.
What does .dockerignore do and why use it ?
.dockerignore file allow you to exclude files from the context like a .gitignore file allow you to exclude file from your git repository.
It help making build faster and lighter by excluding from the context big files or repository that are not used in the build.
docker build has a step where it
tars up the
CONTEXT directory and sends it to the
docker daemon. This is because the
client might not exist on the same server.
tar and network send is why unused files can slow down the build. These happen even if the
daemon runs locally.
Then I put this .dockerignore in container.
nope, don’t do that. The
.dockerignore file is meant to be in the same directory as your
Dockerfile and is intended to speed up the
docker build command by excluding at build time some of the files that won’t be used to build the docker image.