2018.1.4 Pycharm debugger not working with docker containers


 I upgraded to 2018.1.4 and now launching any dockier-compose configured apps with the debugger doesn't work.  The console reads pydev debugger: starting.  The it gives up and prints Gracefully stopping....


I have exactly the same problem now.


Hi! Do you face this problem on macOS? Could you please create a ticket in our bug tracker and attach idea.log from Help | Show Log in ... and your docker and docker-compose versions.


We are facing this problem both on macOS and ubuntu 16.04. I realized that there is already a ticket https://youtrack.jetbrains.com/issue/PY-29850 and added a comment. I didn't find a log file, unfortunately.


Anrous:   Regarding the log file, are you referring to the ones in <your home dir>.PyCharm2018/system/log/idea.log and docker.log?



Yes. I deleted all the log files, reproduced the problem and didn't see any new log files.


Hi, I have the same problem. When I looked at the idea.log, I saw the following error messages.

2018-06-27 10:04:43,126 [ 362863]  ERROR - python.debugger.PyDebugProcess - waitForConnect() must be executed before handshake()

java.lang.IllegalStateException: waitForConnect() must be executed before handshake()

at com.jetbrains.python.debugger.pydev.ClientModeMultiProcessDebugger.handshake(ClientModeMultiProcessDebugger.java:165)

at com.jetbrains.python.debugger.PyDebugProcess.e(PyDebugProcess.java:403)

at com.jetbrains.python.debugger.PyDebugProcess.access$400(PyDebugProcess.java:75)

at com.jetbrains.python.debugger.PyDebugProcess$5.run(PyDebugProcess.java:298)

at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:750)

at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:157)

at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:580)

at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:525)

at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:85)

at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:144)

at com.intellij.openapi.progress.impl.CoreProgressManager$4.run(CoreProgressManager.java:395)

at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:305)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

2018-06-27 10:04:43,128 [ 362865]  ERROR - python.debugger.PyDebugProcess - PyCharm 2018.1.4  Build #PY-181.5087.37

2018-06-27 10:04:43,129 [ 362866]  ERROR - python.debugger.PyDebugProcess - JDK: 1.8.0_152-release

2018-06-27 10:04:43,129 [ 362866]  ERROR - python.debugger.PyDebugProcess - VM: OpenJDK 64-Bit Server VM

2018-06-27 10:04:43,129 [ 362866]  ERROR - python.debugger.PyDebugProcess - Vendor: JetBrains s.r.o

2018-06-27 10:04:43,129 [ 362866]  ERROR - python.debugger.PyDebugProcess - OS: Mac OS X

2018-06-27 10:04:43,129 [ 362866]  ERROR - python.debugger.PyDebugProcess - Last Action: Debug

 My Docker Compose version is 1.21.1.


Mac OS version 10.13.3, PyCharm 2018.1.4, docker-compose version 1.21.1

I have problem with break point. After running my app in container using pycharm Run in Debug mode I saw "Connected to pydev debugger (build 181.5087.37)".

I set breaking point before in code and i expected that code stoped, however it was not happened.  The same code works fine in other guys from team. 

In some cases, when i got system exceptions and code was running in debug mode, debuger stopped in that places. Probably it is problem with slow code syncing  between container and local machine. Does anybody know something about this?


I filed a ticket for this:




Please guys, get on this. It's really frustrating to have paid for the pro edition and not be able to actually do remote debugging.


Please sign in to leave a comment.