Debugging jest from docker - docker

Question

I have a node project running in a docker container that chrome-debugger connects to via port 9229. When using the actual application (as opposed to running the test suite), debugger shows errors/break points just fine.
However, when I run npm run test:e2e from within the docker container, debugger commands, break points, etc are completely ignored. The test suite runs, but it doesn't pick up any breaks.
Admittedly I'm new to both docker & node, but the fact that the app (as opposed to jest) break points are working has me thoroughly confused. If anyone has any ideas on how to get jest break points from a docker container working in chrome-debugger (or vs code for that matter), I'd be really appreciative. Config details below:
docker-compose.yml
pf_debugger:
build: ./pf
image: pf_debugger
container_name: pf_debugger
working_dir: /www
ports:
- "9229:9229"
command: "npm run start:debug"
volumes:
- ./pf:/www
- node_modules:/www/node_modules
depends_on:
- "indy_pool"
- "pf"
networks:
- pf_network
package.json
# ...
"scripts":
"start:debug": "nodemon --config nodemon-debug.json",
"test:e2e": "jest --config ./test/jest-e2e.json",
jest-e2e.json
{
"moduleFileExtensions": ["js", "json", "ts"],
"rootDir": ".",
"testEnvironment": "node",
"testRegex": ".e2e-spec.ts$",
"transform": {
"^.+\\.(t|j)s$": "ts-jest"
}
}
nodemon-debug.json
{
"watch": ["src"],
"ext": "ts",
"inspect": "0.0.0.0:9229",
"exec": "node --inspect=0.0.0.0:9229 --debug -r ts-node/register src/main.ts"
}
launch.json
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "attach",
"name": "Node: Nodemon",
"restart": true,
"sourceMaps": true,
"protocol": "inspector",
"address": "127.0.0.1",
"port": 9229,
"localRoot": "${workspaceRoot}/",
"remoteRoot": "/www/"
},
{
"type": "node",
"name": "e2e-tests",
"request": "launch",
"program": "${workspaceFolder}/node_modules/jest/bin/jest",
"cwd": "${workspaceFolder}",
"console": "integratedTerminal",
"internalConsoleOptions": "neverOpen",
"args": [
"--runInBand",
"--config=test/jest-e2e.json"
]
}
]

Answer 1

For reference, I solved my own problem. Appending --runInBand to the npm:test command ensures breakpoints are obeyed