Rider 2025.2 Debugger: Attach to Docker process CLI

Hello,

I am trying to understand how to programmatically attach Rider debugger to a docker process. The manual workflow (that works) is to:

  • Click the 3 dots
  • Select “Attach to Process”
  • Select the “Docker” tab
  • Click the dropdown and find the correct kubernetes instance
  • Select the process
  • Click “Attach with .NET Debugger”

The issues are:

  • That is a lot of steps to do manually that are the same every time
  • We are using `dotnet watch` which requires the .NET debugger to be attached before any hot reload changes occur for each rude edit

There is the tooling available with `rider attach-to-process` which sounds wonderful, but seems to not support docker processes? Or maybe I was doing something wrong; the documentation is very short. Re-attach to last process is also unavailable; presumably because the process is re-built after rude edits. Ideally the debugger would auto re-attach after a rude edit rebuild, but short of that, any help understanding how to do this via CLI would allow us to get one step closer to scripting the workflow ourselves.

0
1 comment

Hello Ian,

Unfortunately, Rider has limited support of Kubernetes debugging. We have plans to improve this in the scope of RIDER-27214 Remote Debugging application running in Kubernetes and make it easier to attach to specific containers, but there is no ETA yet.

0

Please sign in to leave a comment.