Docker for Windows: certain containers fail to start - "Error response from daemon: bad file descriptor: unknown"

[ropnop]

Description
Certain images fail to start with the latest Docker for Windows. They will silently fail, but with debug mode enabled this is the error message I see:

Error resize: Error response from daemon: bad file descriptor: unknown\r"

Steps to reproduce the issue:

1. On latest Docker for Windows, run the following command:
   docker -D run --rm -it --entrypoint=/bin/bash centos:6

Describe the results you received:
The container does not start and I see the following error:

time="2020-08-11T15:26:16-05:00" level=debug msg="Error resize: Error response from daemon: bad file descriptor: unknown\r"
   time="2020-08-11T15:26:16-05:00" level=debug msg="[hijack] End of stdout"
time="2020-08-11T15:26:17-05:00" level=debug msg="Error resize: Error response from daemon: Container d9daa1c39e1b2048e741028f75312875870548fb106315aae990fc8846caea5c is not running\r"

Describe the results you expected:
The container starts and I enter an interactice /bin/bash. This works with other images, including CentOS 7:

> docker run --rm -it --entrypoint=/bin/bash centos:7
[root@9918ea754d1f /]#

Additional information you deem important (e.g. issue happens only occasionally):
I opened the issue initially with Docker for Win: docker/for-win#7959, but was told to post here instead

Output of docker version:

Client: Docker Engine - Community
 Version:           19.03.12
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        48a66213fe
 Built:             Mon Jun 22 15:43:18 2020
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.12
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       48a66213fe
  Built:            Mon Jun 22 15:49:27 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker info:

Client:
 Debug Mode: false

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 94
 Server Version: 19.03.12
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.19.84-microsoft-standard
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 12.35GiB
 Name: docker-desktop
 ID: SQKM:KCUT:IASF:DYKP:PDYG:QD2N:E2BX:QT6P:QPAH:7NHO:O6RO:QM4L
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 41
  Goroutines: 53
  System Time: 2020-08-11T20:28:34.2936721Z
  EventsListeners: 3
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Additional environment details (AWS, VirtualBox, physical, etc.):
Windows 10 Version 20H2 (OS Build 19042.423)

[thaJeztah]

On Docker for Mac I do get a warning printed, but the container looks to start

docker run -it --rm centos:6
Unable to find image 'centos:6' locally
6: Pulling from library/centos
ff50d722b382: Pull complete
Digest: sha256:dec8f471302de43f4cfcf82f56d99a5227b5ea1aa6d02fa56344986e1f4610e7
Status: Downloaded newer image for centos:6
bash: printf: write error: Interrupted system call
[root@6e254eb6ecf9 /]#

Hmmm. that may actually be a red herring; second time I run a container from that image, I don't see the error printed, so not sure what happened the first time

docker run -it --rm centos:6
[root@c557abdc2f68 /]#

Not seeing the error when running docker on ubuntu 20.04 (on a 5.4.0-29-generic kernel)

docker run -it --rm centos:6
Unable to find image 'centos:6' locally
6: Pulling from library/centos
ff50d722b382: Pull complete
Digest: sha256:dec8f471302de43f4cfcf82f56d99a5227b5ea1aa6d02fa56344986e1f4610e7
Status: Downloaded newer image for centos:6
[root@31e468072cb5 /]#

I'm not sure if this is an issue here or due to how Docker Desktop sets up the Linux distro on WSL2 and/or the proxy used for the Docker remote API 🤔

@simonferquel @djs55 PTAL

[agkrishna101]

HI All,

I was literally new to docker. can some one tell me how to run javaws command inside docker container. I created docker container for my java application and logged into it and ran
"javaws http://ip of container:port which i exposed in docker file/rtccClient/rtcc.jnlp" it says “bash: javaws: command not found”. I create image using ibmcom/websphere-liberty:latest as base image

[thaJeztah]

@agkrishna101 Please keep in mind that the GitHub issue tracker is not intended as a general support forum,
but for reporting bugs and feature requests. For other type of questions, consider using one of;

• the Docker Support Forums - https://forums.docker.com
• the Docker community Slack channel