PhpStorm Docker CLI config creates containers but does not start them

Dear all,

I'm on Windows 10, PhpStorm 2018.2, docker 18.06. When configuring a CLI interpreter via Docker, the daemon connection is working fine and listing the images. As soon as it tries to get the PHP info PhpStorm completely hangs and is only exitable via process termination in the task manager.

I found out via `docker ps -a`  that the container is actually created, but not being started:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
397b73c552141ce1257c1d7eb11eeb2c4d01a11a25fc9f9fc15b36058af73412 sha256:8df243edb1a761b3d8b9e9e11872dfe06308f6fd1bc352cadb33aa45e42c984a "php -dxdebug.remote_enable=0 /opt/.phpstorm_helpers/phpinfo.php" 3 seconds ago Created sad_euler
9bb88feb185a838e60e84a4e0fcdf63527bdc285eeb8eca4526e4471cc5a21ee sha256:8e2049a584f6593a6f5c804a13cb72f89cc5c2797477e7c08dfa12f68667900e "/bin/sh" 21 minutes ago Up 18 minutes phpstorm_helpers_PS-182.4129.45

Manually starting the container via `docker container start <containerId>` then actually runs the command and PhpStorm unfreezes and parses the results. The only entry in idea.log afterwards is:

2018-09-18 22:59:43,315 [2684739] INFO - .CloudSilentLoggingHandlerImpl - Creating container... 

Does anyone have a clue why the container wouldn't get started? Already ran docker system prune to start with a clean slate. Problem reproduces on both machines, but works for colleagues having the exact same settings. 

 

1

Please sign in to leave a comment.