Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,366,173
Community Members
 
Community Events
168
Community Groups

Unexpected EOF while docker build image

Hi,

 

When i execute docker build command to execute dockerfile i am getting unepected EOF.

 

:Generic:testClassesunexpected EOF:Generic:testWarning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at tcp://localhost:2375. Is the docker daemon running?). Using system default: https://index.docker.io/v1/Cannot connect to the Docker daemon at tcp://localhost:2375. Is the docker daemon running?

 

And in docker section i got below logs :

 

2018-01-30 14:18:23,768 INFO exited: watchdog (terminated by SIGKILL; not expected)2018-01-30 14:18:25,039 INFO spawned: 'watchdog' with pid 7352018-01-30 14:18:25,040 INFO exited: watchdog (terminated by SIGKILL; not expected)time="2018-01-30T14:18:24.854235860Z" level=warning msg="libcontainerd: failed to update event timestamp file: write /var/run/docker/libcontainerd/event.ts: cannot allocate memory" 2018-01-30 14:18:26,304 INFO spawned: 'watchdog' with pid 7362018-01-30 14:18:26,306 INFO exited: watchdog (terminated by SIGKILL; not expected)time="2018-01-30T14:18:26.137811940Z" level=warning msg="libcontainerd: failed to update event timestamp file: write /var/run/docker/libcontainerd/event.ts: cannot allocate memory" 2018-01-30 14:18:28,572 INFO spawned: 'watchdog' with pid 7372018-01-30 14:18:28,573 INFO exited: watchdog (terminated by SIGKILL; not expected)2018-01-30 14:18:31,637 INFO spawned: 'watchdog' with pid 738time="2018-01-30T14:18:31.615986819Z" level=warning msg="libcontainerd: failed to update event timestamp file: write /var/run/docker/libcontainerd/event.ts: cannot allocate memory" 2018-01-30 14:18:31,871 INFO exited: watchdog (terminated by SIGKILL; not expected)2018-01-30 14:18:32,872 INFO gave up: watchdog entered FATAL state, too many start retries too quickly2018-01-30 14:18:36,993 INFO exited: pipelines (terminated by SIGKILL; not expected)2018-01-30 14:18:38,002 INFO spawned: 'pipelines' with pid 7392018-01-30 14:18:39,004 INFO success: pipelines entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2018-01-30 14:19:33,444 INFO exited: pipelines (terminated by SIGKILL; not expected)2018-01-30 14:19:34,456 INFO spawned: 'pipelines' with pid 7432018-01-30 14:19:34,785 INFO exited: pipelines (terminated by SIGKILL; not expected)2018-01-30 14:19:35,796 INFO spawned: 'pipelines' with pid 744supervisor: couldn't exec pipelines: ENOMEMsupervisor: child process was not spawned2018-01-30 14:19:35,847 INFO exited: pipelines (exit status 127; not expected)2018-01-30 14:19:37,861 INFO spawned: 'pipelines' with pid 745supervisor: couldn't exec pipelines: ENOMEMsupervisor: child process was not spawned2018-01-30 14:19:38,105 INFO exited: pipelines (exit status 127; not expected)2018-01-30 14:19:38,113 INFO exited: dockerd (terminated by SIGKILL; not expected)2018-01-30 14:19:38,113 INFO reaped unknown pid 332018-01-30 14:19:41,120 INFO spawned: 'pipelines' with pid 7462018-01-30 14:19:42,123 INFO success: pipelines entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

 

 

Can anyone help me understand what is the problem exactly and how to solve it ?

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events