Of course I think I have everything set up right, but this is all new to me.
I have a Docker container running Node.js v8.11.4 under Alpine 3.6. I set up WebStorm 2018.2.2 with Docker according to the help files and with Automatic Configuration, and I followed the instructions under "Debugging a Node.js application in a Docker container". I set breakpoints as early as I could in the source.
When I hit the debug icon, WebStorm builds a Docker image, runs it, and I see the "Debugger listening on" message on the console. However, the WebStorm debugger never seems to connect. I never hit a breakpoint, and if I press the pause button on the debugger nothing happens.
I can connect to the debugger port from Terminal, and /json/list gives me the same UUID I see in the WebStorm console. It uses the containers internal network address in the webSocketDebuggerUrl field instead of the Docker server address, but that shouldn't matter as the "Debugger listening on" message shows the correct IP address to connect to.
I don't see anything fishy in the idea.log logfile and the docker.log file is empty.
When I run commands inside the Docker container, I see that Node is running and the debugger port is open, but there are no listeners other than the debugger port, which is consistent with the app never getting started (and opening its ports).
OK, I see node is stopping on startup because WebStorm is passing the deprecated "--debug-brk" flag. I can't seem to get that to go away. If I add "--inspect" to the Node parameters, "--debug-brk" remains even if I add "--inspect-brk". If I add "--inspect-brk" without "--inspect", WebStorm fails to assign an address, it defaults to 127.0.0.1, and I cannot connect to it.
I can connect to the debugger with Chrome DevTools and continue the process, but still WebStorm never connects.
How do I move forward to get remote debugging working?