Harshal Shah
Harshal Shah
Sure, We are running on EKS, ~~~ Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T12:36:28Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.6-eks-5047ed", GitCommit:"5047edce664593832e9b889e447ac75ab104f527", GitTreeState:"clean", BuildDate:"2019-08-21T22:32:40Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"} ~~~...
An additional bit of information: looking for container ID in dockerd logs we see the following messages: ~~~ Jan 11 06:51:04 ip-172-23-105-205 dockerd[22916]: time="2019-01-11T06:51:04.084376905Z" level=error msg="containerd: get exit status" error="containerd:...
@nerdherdx since we were using kops, we changed our ec2 images from ubuntu xenial to ubuntu bionic and our docker version from 17.03 to 18.06
@honnix We have not faced this problem on docker `18.x`
I'm facing this problem again in docker 19.03 ~~~ Client: Version: 19.03.6-ce API version: 1.40 Go version: go1.13.4 Git commit: 369ce74 Built: Fri Mar 6 23:25:53 2020 OS/Arch: linux/amd64 Experimental:...
@zoombinis we are seeing the same issue as well with following docker version ~~~ docker version Client: Version: 19.03.6-ce API version: 1.40 Go version: go1.13.4 Git commit: 369ce74 Built: Fri...