Hey any news on this one?

If you manually insert a debugger; line into your code, it will work, but it will try to open a file on the host machine, with a path from the docker container.
In Node.js debugger, you just had to specify the remoteRoot in launch.json example in the docs. I don't think remoteRoot exists in Bun extension for VS Code.

I captured the websocket communication using Wireshark just to confirm.

1. VS Code sends the breakpoint

{"id":6,"method":"Debugger.setBreakpointByUrl","params":{"url":"/home/matthew/Projects/bun-test/src/main.ts","lineNumber":0}}

2. Bun debugger inside docker acknowledges

{"result":{"breakpointId":"/home/matthew/Projects/bun-test/src/main.ts:0:0","locations":[]},"id":6}

3. Bun reports parsed scripts, here is the one (id 1533) with debugger; on line 5:

{"method":"Debugger.scriptParsed","params":{"scriptId":"1533","url":"/usr/src/app/src/main.ts","startLine":0,"startColumn":0,"endLine":11,"endColumn":0,"isContentScript":false,"sourceURL":"/usr/src/app/src/main.ts","sourceMapURL":"[...]", ...

3. Bun debugger stops on the line with debugger;

{"method":"Debugger.paused","params": {"callFrames": [{"callFrameId": "{\"ordinal\":0,\"injectedScriptId\":1}","functionName": "","location": {"scriptId": "1533", ...

4. VS Code tries to open /usr/src/app/src/main.ts

In this example case, setting remoteRoot to /usr/src/app should simply fix the problem, but that option is just not available in Bun debugger for VS Code as far as I know.

I wanted to submit a patch myself, this seems like an easy fix, but I never touched Bun code base so I have no idea where to add my fix. I will leave it to the developers.

@ZeldOcarina @matepaiva
The workaround for it is to change the WORKDIR in the Dockerfile to the same path as on the host system. In my base it's WORKDIR /home/matthew/Projects/bun-test. It is a nasty workaround, but works well enough.

There's an easier fix I've applied: I switched everything to npm!

There's an easier fix I've applied: I switched everything to npm!

😆😆😆 Yeah, I guess Bun is not ready to be a plug&play Node.js replacement... I hope it will eventually get there!

Will this get fixed anytime soon?

I wanted to submit a patch myself, this seems like an easy fix, but I never touched Bun code base so I have no idea where to add my fix. I will leave it to the developers.

@ZeldOcarina @matepaiva The workaround for it is to change the WORKDIR in the Dockerfile to the same path as on the host system. In my base it's WORKDIR /home/matthew/Projects/bun-test. It is a nasty workaround, but works well enough.

This was actually a really good fix for us. While beeing hacky, we build a portable solution.

This is our dockerfile (which also shows build secrets, which works also with the solution)

ARG BUN_VERSION=1.1.26
FROM oven/bun:${BUN_VERSION}-alpine as development

ARG WORKDIR_ENV
WORKDIR ${WORKDIR_ENV}
COPY package.json bunfig.toml bun.lockb ./
RUN --mount=type=secret,id=gitlab_npmrc,target=${WORKDIR_ENV}/.npmrc bun install --ignore-scripts --frozen-lockfile

Now you can set in your docker-compose file. Important: You have to expose the LOCAL_PWD env var to your system. We did not found a way that docker-compose could infer the pwd correctly. In your build pipeline you can now expose e.g. /app as the env var.

 build:
      context: .
      dockerfile: '.docker/Dockerfile.node'
      target: development
      args:
        - WORKDIR_ENV=$LOCAL_PWD

This is the launch config we use:

{
  "version": "0.2.0",
  "configurations": [
      {
          "name": "bun (docker)",
          "type": "bun",
          "request": "attach",
          "url": "ws://localhost:6499/tq1bwri63p",
      }
  ]
}

We still would be happy if bun fixes this by adding the the root properties

is nobody using bun in docker? i'm very frustrated

the debug id in the url can be fixed with a custom prefix, eg:

bun run --hot --inspect=127.0.0.1:6499/debug src/index.ts

with this config & the docker container running in network_mode: host i can get the debugger working ONLY in the browser inspector. the VS code debugger will attach to the debugger server but none of the breakpoints work

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "bun",
      "request": "attach",
      "name": "Attach to Bun",
      "url": "ws://127.0.0.1:6499/debug",
    }
  ]
}

1. why must we have this running in host network mode? is this a technical limitation? for security?
2. what may be going wrong with the vs code debugger? I can't get any debug logs for this to find out why the breakpoints don't function

Use tsx, it's great for debugging in VSCode!