WSL2 fails to start one image

pf-mike-breaton commented 4 years ago

I have one image in particular that fails to start under D4W WSL2 but runs fine under hyper-v version.

docker run --rm -it caapim/gateway:9.2.00

[ ] I have tried with the latest version of my channel (Stable or Edge)
[ ] I have uploaded Diagnostics
Diagnostics ID:

Expected behavior

container starts and outputs following text:

> docker run --rm -it caapim/gateway:9.2.00
apim-provisioning: INFO: checking if a Consul server has been set in the SSG_CONSUL_IP environment variable
apim-provisioning: INFO: no Consul server set via the SSG_CONSUL_IP environment variable
apim-provisioning: INFO: checking for an etcd server
apim-provisioning: INFO: no etcd server available (neither ETCDCTL_ENDPOINT nor ETCDCTL_DISCOVERY_SRV were set in the environment
apim-provisioning: INFO: validating the collected config
apim-provisioning: ERROR: need to set env var SSG_CLUSTER_COMMAND to either "create" or "join"

Actual behavior

Under WSL2, container starts and exits immediately with no messages outputted

> docker run --rm -it caapim/gateway:9.2.00
>

Information

This has been happening for all prior versions of D4W WSL2 and was wondering if there is some workaround to getting this particular image working

The image is an older version (there is now 9.3 and 9.4 version which seem to work) but we only have license for 9.2.

Windows Version: 19041.208
Docker Desktop Version: 2.3.0.2 (45183)
Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No

Steps to reproduce the behavior

from command line, run: docker run --rm -it caapim/gateway:9.2.00

docker-robott commented 4 years ago

Issues go stale after 90 days of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30 days 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

pf-mike-breaton commented 4 years ago

/lifecycle frozen

iciuperca commented 3 years ago

I'm having the same issue, image works under hyper-v but silently fails under wsl2 as described by the parent.

docker / for-win