Created
October 17, 2014 08:17
-
-
Save dasgoll/caa96065d9b83d9044e1 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| What does 'Sending build context to Docker daemon' mean? | |
| [root@centos65vm1 1]# docker build -t ubtest . | |
| Sending build context to Docker daemon 2.56 kB | |
| Quick and dirty answer: the client is tar/compressing the directory (and all subdirectories) where you executed docker build. Yeah, that's right. If you execute this in your root directory, your whole drive will get tar'd and sent to the docker daemon. Caveat something. Generally that's a mistake you only make once. | |
| Anyways, the build gets run by the daemon, not the client, so the daemon needs the whole directory that included (hopefully) the Dockerfile and any other local files needed for the build. That's the context. | |
| Would probably be good to also mention that this has to happen this way because the client and daemon may not even run on the same machine, so without this "context" the daemon machine wouldn't have any other way to get files for ADD or otherwise. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment