Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Sending build context to Docker daemon (it doesn't stop)

(UBUNTU) I create my dockerfile with touch dockerfile and I do sudo vim dockerfile. the code inside is:

FROM ubuntu:12.00
CMD echo Hello World!!

So I do sudo docker build . . The shell prints me

Sending build context to Docker daemon TOT kB

TOT is the number of GB that the shell download and Now I have 10.40 GB. IS it possible or I wrong something?

like image 976
Doppu Avatar asked Mar 31 '17 10:03

Doppu


People also ask

What does it mean sending build context to Docker daemon?

The Docker build context consists of files or folders located at the particular path or URL. During the build, those files are sent to the Docker daemon so that the image can use them as files.

How do you gracefully stop a Docker container?

docker rm -f The final option for stopping a running container is to use the --force or -f flag in conjunction with the docker rm command. Typically, docker rm is used to remove an already stopped container, but the use of the -f flag will cause it to first issue a SIGKILL.

How do I start and stop Docker daemon?

Start the daemon manually You may need to use sudo, depending on your operating system configuration. When you start Docker this way, it runs in the foreground and sends its logs directly to your terminal. To stop Docker when you have started it manually, issue a Ctrl+C in your terminal.

Why is my Docker daemon not running?

Occasionally, the user may get the error “the docker daemon is not running” because of missing dependencies. To use Docker Daemon the WSL must be activated on your machine. The below output clears that the Docker is installed on the system.


2 Answers

mv your Dockerfile to an empty folder, and build it. When build a docker image, docker will "use" all files in current folder as its "context". You can also create a .dockerignore file to exclude files or directories like .gitignore.

like image 161
dormi330 Avatar answered Sep 30 '22 12:09

dormi330


Try this command :

docker build -t go_grpc:1.10 - < Dockerfile
like image 34
Alex Punnen Avatar answered Sep 30 '22 10:09

Alex Punnen