Closed agsmorodin closed 8 years ago
@agsmorodin Thank you for opening a separate issue. Is there any sequence of actions that triggers this error, something interesting in the Manager logs? Never encountered this issue on long running clusters since we fixed the refresh loop but never tried on CentOS (or RHEL 7.1) with an older kernel (3.10
is the strict minimum required) :confused:
By any chance, is one of the containers in your cluster in the Dead
state when this occurs? Printing the Manager logs just before the panic as well as the output of docker ps -a
might help. Thanks!
Thanks @agsmorodin - I think #1414 fixes this.
@agsmorodin - would you mind trying with master?
You can run the dockerswarm/swarm:master
image which will contain this fix.
Closing this in the meantime - @agsmorodin please re-open if the problem continues.
Thanks!
Fixed by #1465
I get the following exception that I am experiencing from time to time with latest docker. I get this error almost every day.
docker -v Docker version 1.9.0, build 76d6bc9
and swarm : docker exec -ti e360 /swarm --version swarm version 1.0.0 (087e245).
System details as requested ( I am using docker machine with centos 7.1 image ).
uname -a