Cannot debug in WSL

The solution contains several projects and two of them are ASP.NET Core WebApps. Each WebApp has a Dockerfile and the solution has a docker-compose.yml file to run the apps together. I am using the Windows version of Rider, my machine has a configured WSL2 instance with Ubuntu. In the Rider settings, Docker is configured to connect to WSL. I created a Docker Compose configuration in Rider to use my docker-compose.yml file and it works fine when I run it - it creates the required containers and I can reach them. But when I try to debug using this configuration, the debugging session attempts to start but an error prints to the console:

exec /opt/rider-debugger/linux-musl-x64/dotnet/dotnet: no such file or directory

It seems like Rider expects a debugger installed on the WSL instance and cannot find it. How can I install it or resolve this issue in another way?

0
5 comments

Have a try with the latest 2024.2.5, we fixed some problems of RiderRemoteDebugger installation. 

By the way, you can specify the Docker Desktop use WSL2 as the deamon backend. You don't have to set up docker engine in WSL.

0

The in-container debugging system worked perfectly before I updated Rider to version 2024.2.5. Now it runs services but doesn't connect to them. Nothing has changed except the Ride upgrade. Horrible work, folks! 

0

Shumutun Try to rebuild the container with Rider (with Fast Mode disabled). During the rebuilding, the new version of debugger backend will be bring to the container.

0

I use docker-compose to build my multiservice setup. All services in the docker-compose are built from a “dev” Dockerfile: 

FROM mcr.microsoft.com/dotnet/aspnet:8.0
WORKDIR /app
COPY ["bin/Debug/net8.0", "."]
ENTRYPOINT ["dotnet", "<my_proj_name>.dll"]

on a successful project build: 

if docker info > /dev/null 2>&1; then
    docker build -f ./DockerfileDev -t <my_proj_name>:latest .
fi

which was extremely fast. 

Previously I could add breakpoints and debug all my services in this setup simultaneously, but I lost this feature after upgrading. It looks like I should roll back to the previous version and stay on it without prolonging the subscription until you add something unimaginable to Rider that will make me spend additional time rebuilding my setup to make it work with a new version and start paying for Rider again. 

 

0

Could you please share the full docker compose and DockerFile so that we can try to reproduce the issue? By default, with docker fast mode enabled, the application will be built locally and mounted into the container during execution. 

You can also share the full log bundle with us, and we are glad to look into the problem. Please upload the files to our server and share the Upload ID.

 

0

Please sign in to leave a comment.