ERRO[106389] error waiting for container: EOF #1941

gillez · 2017-08-07T09:10:16Z

Expected behavior

Docker image container to run continuously for a long period

Actual behavior

At some point it exited with the following error:
ERRO[106389] error waiting for container: EOF

The process was started on Friday morning and the error was noticed on Monday morning so the error happened at some point on Friday or over the weekend. The system wasn't in use over this time and there's no timestamp so I can't say exactly how long it was up for before this happened.

Information

Full output of the diagnostics from "Diagnose & Feedback" in the menu
Diagnostics have been uploaded. The ID is:
01D84A34-736C-471B-BA62-EEA240BB287C

Docker for Mac: version: 17.06.0-ce-mac19 (4cdec4294a50b2233146b09469b49937dabdebdd)
macOS: version 10.12.5 (build: 16F73)
logs: /tmp/01D84A34-736C-471B-BA62-EEA240BB287C/20170807-095022.tar.gz
[OK]     db.git
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     db
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     slirp
[OK]     osxfs
[OK]     moby-console
[OK]     logs
[OK]     docker-cli
[OK]     menubar
[OK]     disk

Steps to reproduce the behavior

The image is not uploaded anywhere so you won't be able to run the same image.
But the steps were just to run the image with "docker run" and leave it for a day or two.
As I'm not expecting anyone to reproduce this I would really just like to know what the "error waiting for container" EOF error means, and whether the diagnostics show anything.

The text was updated successfully, but these errors were encountered:

evilstreak · 2017-08-17T12:33:23Z

I also had my container terminating with ERRO[…] error waiting for container: EOF.

It was fine running a low intensity task, but when running something that used more CPU it failed on every run. Increasing the amount of available CPU (from 1 to 3) and memory (from 2G to 8G) through the Docker For Mac preferences resolved the issue.

I could see no indication anywhere that resource limits were the issue; if that is the issue it would be great if that was made clearer.

This is just anecdotal, but hopefully it helps for you!

filipesperandio · 2017-09-18T20:56:36Z

Faced the same problem a bunch of times over the past few days, always running variations of the same container. High intense CPU and RAM (container limited to 512M) and lots of console output.

addynaik · 2017-10-01T12:05:43Z

I have the same issue and it just started recently - may be after the update? also another similarity with OP, my image is also a private custom image. I dont know if this would be relevant but a point of consideration.

StefanoFioravanzo · 2017-10-19T09:04:00Z

I have been trying to run a Django web app inside a docker container for the past few days, after some time (it may be hours or days) it crashes with ERRO[203312] error waiting for container: unexpected EOF.

There is neither high CPU/Mem usage nor lots of console output, so I don't think this is a resource limit issue. Also, I am not limiting the resources used by the container.

I also tried to add --restart on-failure but when the container crashed it does not restart automatically.

I am running Docker version 17.09.0-ce, build afdb6d4 on Ubuntu 16.04.3 LTS.

gillez · 2017-10-19T09:15:48Z

Our behaviour is similar to Stefano. Increasing the resources doesn't help. Does anyone know what this error actually means?

Also, is Docker on Mac suitable and recommended for production?

filipesperandio · 2017-10-19T11:45:52Z

Also, is Docker on Mac suitable and recommended for production?

I use it for development, but considering it for production would freak me out

Drwhit · 2017-10-21T20:56:18Z

I just started getting this error yesterday too. I am using Rstudio R notebooks. Whether I have one or two containers running at the same time, they both crash.

alexgorbatchev · 2017-10-24T03:30:19Z

FWIW Seeing the same on Windows 10 host. Diagnostics ID 61722AC9-9FB3-423B-955E-160FEE0D0238/2017-10-23_20-31-56

antonkulaga · 2017-10-26T21:22:02Z

I have the same issue on Ubuntu (on Azure VM) when running containers that consume a lot of cores/memory. Looks like it is general docker issue

feisuzhu · 2017-11-29T10:47:26Z

We are experiencing this on a Mesos/Marathon deploy (Linux cluster, not on Mac).

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 4 100 4 0 0 850 0 --:--:-- --:--:-- --:--:-- 1000
pong % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 4 100 4 0 0 802 0 --:--:-- --:--:-- --:--:-- 1000
pong % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 4 100 4 0 0 786 0 --:--:-- --:--:-- --:--:-- 1000
pongtime="2017-11-29T18:37:45+08:00" level=error msg="error waiting for container: unexpected EOF"
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 4 100 4 0 0 829 0 --:--:-- --:--:-- --:--:-- 1000
pongW1129 18:38:45.278836 13917 main.cpp:380] Health check failed Command check failed with reason: status still pending after timeout 30secs

melissachang · 2018-02-23T01:08:47Z

I am seeing this on Debian Google Compute Engine VM with 2 VCPU and 10.5 GB memory.

melchang@elasticsearch-not-cos:$ docker -v
Docker version 17.12.0-ce, build c97c6d6
melchang@elasticsearch-not-cos:$ uname -a
Linux elasticsearch-not-cos 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux

I wonder if there's an earlier version of docker that won't have this issue.

DmitryMandrik · 2018-02-23T09:01:35Z

Hi guys! Are there any news about this ticket?
I run cucumber framework inside the container for 10 hours. Seeing the same issue almost every run.

melissachang · 2018-02-23T17:29:03Z

GCE VM host when I saw this problem: 2 VCPU, 10.5 TB memory
GCE VM host when I don't see this problem: 12 VCPU, 31 GB memory

I was indexing a 590 MB BigQuery table that has 4.4 million rows.

Miserlou · 2018-03-13T20:05:05Z

I updated Docker to the latest today and am now seeing this error every few minutes, corresponding with a Docker for Mac restart or total crash.

DmitryMandrik · 2018-03-14T07:40:44Z

to the latest stable 17.12.0-ce-mac55?

Miserlou · 2018-03-14T13:47:26Z

I think my error (and maybe this error?) is related to: #2690

DmitryMandrik · 2018-03-14T13:54:33Z

I have the error ERRO[106389] error waiting for container: EOF. BTW I ran my framework with Docker on Ubuntu and there was no error.

akimd · 2018-03-15T09:23:55Z

Hi guys! As of today this issue has no Diagnostics from a recent version of Docker for Mac. Unless someone provides some, I'll close this issue.

https://download.docker.com/mac/edge/Docker.dmg

DmitryMandrik · 2018-03-22T11:01:11Z

Hi guys! Is there any new workaround to avoid this issue?

DmitryMandrik · 2018-03-26T08:13:54Z

Hi @akimd , here is the issue reproduced on the edge version 18.03.0-ce-rc4-mac57 (23360)
ID: C9ECD2DB-9976-4F64-BFDF-BBB3DC40E18E

Docker for Mac: version: 18.03.0-ce-rc4-mac57 (dd2831d4b7421cf559a0881cc7a5fdebeb8c2b98)
macOS: version 10.13.3 (build: 17D102)
logs: /tmp/C9ECD2DB-9976-4F64-BFDF-BBB3DC40E18E/20180326-030754.tar.gz
failure: com.docker.vpnkit is not running
[ERROR]  vpnkit
         Unexpected error ((Failure
  "Error connecting socket to 9p endpoint unix:/Users/wheniwork/Library/Containers/com.docker.docker/Data/s51: Unix.Unix_error(Unix.ECONNREFUSED, \"connect\", \"\")")) connecting to /Users/wheniwork/Library/Containers/com.docker.docker/Data/s51
         com.docker.vpnkit is not running
         vpnkit check failed with: Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")
[OK]     vmnetd
[OK]     dns
[ERROR]  driver.amd64-linux
         com.docker.driver.amd64-linux is not running
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     kubernetes
[OK]     files
[OK]     env
[OK]     virtualization kern.hv_support
[ERROR]  osxfs
         com.docker.osxfs is not running
[OK]     moby-console
[OK]     logs
[ERROR]  docker-cli
         Connection refused (ECONNREFUSED) connecting to /var/run/docker.sock: check if service is running
         Connection refused (ECONNREFUSED) connecting to /Users/wheniwork/Library/Containers/com.docker.docker/Data/s60: check if service is running
         docker ps failed
[OK]     disk

DmitryMandrik · 2018-03-27T15:08:26Z

@akimd do you have any news? When do you plan to proceed with the issue?

akimd · 2018-03-28T10:09:10Z

I had a look, and it doesn't not ring any bell. Others might have better ideas.

edupo · 2018-04-10T11:07:22Z

Same here with this random error. Docker 17.12.0-ce

docker-robott · 2018-07-30T18:41:24Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

wkoziej · 2018-08-27T13:29:45Z

Hi
I had similar error.
Docker version 17.12.1-ce, build 7390fc6
Docker had crushed after several days running tensorboard

letmaik · 2018-10-29T08:31:17Z

Same issue here on 18.06.1-ce-win73.
EDIT: After that crash I couldn't do docker ps -a anymore ("Error response from daemon: An invalid argument was supplied.") and had to restart Docker.

yucolabjames · 2019-01-10T03:40:06Z

Running into the same problem here. But I can see docker is still working when i run htop.

simonm3 · 2019-01-27T10:10:13Z

Same problem. On windows. Docker still running. Can still "docker ps -a". Container still running but can't exec into it.

Thf772 · 2019-06-17T09:10:13Z

I have run into that problem today when trying to run pi-gen on Windows. Afterwards, I couldn't use any docker command either from Powershell or WSL Bash.

Error response from daemon: L’adresse demandée n’est pas valide dans son contexte.
Error response from daemon: Requested address is not valid in its context.

Restarting Docker Desktop restores access to the Docker command.

DarrienG · 2019-08-07T16:59:51Z

This happens sometimes when docker crashes or is stopped. It isn't necessarily indicative of a failure.

RobertoDonPedro · 2020-02-29T09:23:36Z

Same issue here on GKE running Docker version 18.09.7

ERRO[0209] error waiting for container: unexpected EOF

Neither CPU nor Memory reach their limits. The node logs just say

FrequentDockerRestart
FrequentKubeletRestart

Any ideas how to find the cause of this issue?

docker-robott · 2020-06-25T03:02:57Z

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

jasonbivins added osx/10.12.x status/triage version/17.06.0-ce-mac19 labels Aug 7, 2017

Miserlou mentioned this issue Mar 14, 2018

Extreme Instability Since Latest Update to Version 17.12.0-ce-mac55 (23011) #2699

Closed

docker-robott added the version/18.03.0-ce-rc4-mac57 label Mar 26, 2018

docker-robott added the lifecycle/stale label Jul 30, 2018

docker-robott closed this as completed Apr 4, 2020

docker locked and limited conversation to collaborators Jun 25, 2020

docker-robott added the lifecycle/locked label Jun 25, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ERRO[106389] error waiting for container: EOF #1941

ERRO[106389] error waiting for container: EOF #1941

gillez commented Aug 7, 2017 •

edited by akimd

Loading

evilstreak commented Aug 17, 2017

filipesperandio commented Sep 18, 2017

addynaik commented Oct 1, 2017

StefanoFioravanzo commented Oct 19, 2017 •

edited

Loading

gillez commented Oct 19, 2017

filipesperandio commented Oct 19, 2017

Drwhit commented Oct 21, 2017

alexgorbatchev commented Oct 24, 2017 •

edited

Loading

antonkulaga commented Oct 26, 2017

feisuzhu commented Nov 29, 2017 •

edited

Loading

melissachang commented Feb 23, 2018 •

edited

Loading

DmitryMandrik commented Feb 23, 2018 •

edited

Loading

melissachang commented Feb 23, 2018 •

edited

Loading

Miserlou commented Mar 13, 2018

DmitryMandrik commented Mar 14, 2018

Miserlou commented Mar 14, 2018

DmitryMandrik commented Mar 14, 2018

akimd commented Mar 15, 2018

DmitryMandrik commented Mar 22, 2018

DmitryMandrik commented Mar 26, 2018 •

edited

Loading

DmitryMandrik commented Mar 27, 2018

akimd commented Mar 28, 2018

edupo commented Apr 10, 2018

docker-robott commented Jul 30, 2018

wkoziej commented Aug 27, 2018

letmaik commented Oct 29, 2018 •

edited

Loading

yucolabjames commented Jan 10, 2019

simonm3 commented Jan 27, 2019

Thf772 commented Jun 17, 2019 •

edited

Loading

DarrienG commented Aug 7, 2019

RobertoDonPedro commented Feb 29, 2020

docker-robott commented Jun 25, 2020

ERRO[106389] error waiting for container: EOF #1941

ERRO[106389] error waiting for container: EOF #1941

Comments

gillez commented Aug 7, 2017 • edited by akimd Loading

Expected behavior

Actual behavior

Information

Steps to reproduce the behavior

evilstreak commented Aug 17, 2017

filipesperandio commented Sep 18, 2017

addynaik commented Oct 1, 2017

StefanoFioravanzo commented Oct 19, 2017 • edited Loading

gillez commented Oct 19, 2017

filipesperandio commented Oct 19, 2017

Drwhit commented Oct 21, 2017

alexgorbatchev commented Oct 24, 2017 • edited Loading

antonkulaga commented Oct 26, 2017

feisuzhu commented Nov 29, 2017 • edited Loading

melissachang commented Feb 23, 2018 • edited Loading

DmitryMandrik commented Feb 23, 2018 • edited Loading

melissachang commented Feb 23, 2018 • edited Loading

Miserlou commented Mar 13, 2018

DmitryMandrik commented Mar 14, 2018

Miserlou commented Mar 14, 2018

DmitryMandrik commented Mar 14, 2018

akimd commented Mar 15, 2018

DmitryMandrik commented Mar 22, 2018

DmitryMandrik commented Mar 26, 2018 • edited Loading

DmitryMandrik commented Mar 27, 2018

akimd commented Mar 28, 2018

edupo commented Apr 10, 2018

docker-robott commented Jul 30, 2018

wkoziej commented Aug 27, 2018

letmaik commented Oct 29, 2018 • edited Loading

yucolabjames commented Jan 10, 2019

simonm3 commented Jan 27, 2019

Thf772 commented Jun 17, 2019 • edited Loading

DarrienG commented Aug 7, 2019

RobertoDonPedro commented Feb 29, 2020

docker-robott commented Jun 25, 2020

gillez commented Aug 7, 2017 •

edited by akimd

Loading

StefanoFioravanzo commented Oct 19, 2017 •

edited

Loading

alexgorbatchev commented Oct 24, 2017 •

edited

Loading

feisuzhu commented Nov 29, 2017 •

edited

Loading

melissachang commented Feb 23, 2018 •

edited

Loading

DmitryMandrik commented Feb 23, 2018 •

edited

Loading

melissachang commented Feb 23, 2018 •

edited

Loading

DmitryMandrik commented Mar 26, 2018 •

edited

Loading

letmaik commented Oct 29, 2018 •

edited

Loading

Thf772 commented Jun 17, 2019 •

edited

Loading