{"id":347071,"date":"2023-08-16T15:32:55","date_gmt":"2023-08-16T14:32:55","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=dotnet&p=347071"},"modified":"2023-08-16T15:39:24","modified_gmt":"2023-08-16T14:39:24","slug":"debugging-docker-and-docker-compose-solutions-with-jetbrains-rider","status":"publish","type":"dotnet","link":"https:\/\/blog.jetbrains.com\/en\/dotnet\/2023\/08\/16\/debugging-docker-and-docker-compose-solutions-with-jetbrains-rider","title":{"rendered":"How To Debug Docker and Docker Compose Solutions with JetBrains Rider"},"content":{"rendered":"\n

Docker has become an integral part of a developer’s workflow, and docker-compose<\/code> helps you build complex distributed solutions from your development to the production environment. In recent releases of JetBrains Rider, we added Fast-Mode Docker Support<\/strong><\/a>. In short, your development feedback loop just got a lot faster.\u00a0<\/p>\n\n\n\n

We’ve noticed folks are still trying to understand this workflow, and we thought we’d write an updated walkthrough to help you debug both standalone container apps and docker-compose<\/code> solutions. Let’s go ahead and get started.<\/p>\n\n\n\n

What is Docker and Docker Compose?<\/h2>\n\n\n\n

Docker<\/a> is a containerization technology that allows you to package and deploy your application to a hosting destination. Containerization is a technique many vendors use, but Docker is the space’s most well-known commercial tooling provider, with 18 million developers using it worldwide.<\/p>\n\n\n\n

Core to Docker is the concept of containers. With containers, users can avoid common issues found with setting up environments. For example, container images can define dependencies, environment variables, and disk volumes through codification. In addition, a code-based configuration helps reduce common mistakes when manual processes are in place. While containerizing one application can be helpful, most modern solutions include several services talking to each other, and that’s where docker-compose<\/code> comes in.<\/p>\n\n\n\n

Docker Compose is a tool to define multi-container applications through a carefully specified configuration. To start with, a docker-compose<\/code> YAML file can use images defined by you or a third-party organization to orchestrate a distributed solution. In addition to containers, your environment definition can allocate shared resources, such as data volumes and networking. Docker Compose commands can also intelligently manage an environment, only recreating the changes in your solution. Finally, Docker Compose applies to all deployment environments, including CI\/CD pipelines.
To start with Docker, you’ll need an installed version of Docker Desktop<\/strong><\/a> in your development environment.<\/p>\n\n\n\n

Rider and Docker Pre-flight Check<\/h2>\n\n\n\n

After installing Docker Desktop, you should check that Rider recognizes your Docker Desktop installation. <\/p>\n\n\n\n

First, start a new instance of JetBrains Rider and go to Settings <\/strong>and navigate to Build, Execution, Deployment | Docker. <\/strong>You should see that JetBrains Rider has recognized your installation of Docker Desktop. <\/strong>If you don’t see these settings, you likely don’t have the Docker <\/strong>plugin installed or enabled.<\/p>\n\n\n\n

\"Settings<\/figure>\n\n\n\n

If you don’t see Docker in the settings window, ensure you have correctly installed Docker Desktop.<\/strong><\/p>\n\n\n\n

Next, you can open any existing project, and open the Services <\/strong>window. You should see the familiar Docker whale. You can connect to the Docker Desktop instance by double-clicking the whale icon. Once connected, you can see any running containers alongside images, networks, and volumes.<\/p>\n\n\n\n

\"Services<\/figure>\n\n\n\n

If you do not see the Docker icon, click the “+” symbol and choose Docker Connection. At this point, you can add a new connection.<\/p>\n\n\n\n

Great. You should now be able to get started with .NET containerized development.<\/p>\n\n\n\n

Debugging Docker containers with Rider<\/h2>\n\n\n\n

I’ll be using an ASP.NET Core<\/a> solution with two web applications. When creating a new ASP.NET Core project, you’ll also have the chance to opt into Docker.<\/strong> Choosing Docker will add a DockerFile<\/code> to your project.<\/p>\n\n\n\n

\"Connected<\/figure>\n\n\n\n

With a DockerFile<\/code> open, you can run the container. Before running the container, you can edit the run configuration to expose the container ports to the host. You’ll need the ports exposed to the host environment to hit an API endpoint.<\/p>\n\n\n\n

\"JetBrains<\/figure>\n\n\n\n

Now that your container is running, you can click the Debug <\/strong>button in the run toolbar. Furthermore, remember to add a breakpoint to see the debugger in action. Then, using the HTTP Client in Rider, you can call an endpoint to stop on your breakpoint.<\/p>\n\n\n\n

\"Debugging<\/figure>\n\n\n\n

Debugging Docker Compose with Rider<\/h2>\n\n\n\n

JetBrains Rider recently added a feature to help define a docker-compose.yml<\/code> file. JetBrains Rider will add each service to a central docker-compose.yml<\/code> file with a straightforward right-click of any ASP.NET Core project and then selecting “Docker Compose file”.<\/strong><\/p>\n\n\n\n

I’ve added two ASP.NET Core web projects to a docker-compose.yml<\/code> file, altering the ports in my orchestrated application. Then, by clicking the play button at the top of the file, we get a run configuration and the application containers running in the services window.<\/p>\n\n\n\n

\"Docker<\/figure>\n\n\n\n

You can now use the Debug button like debugging a single Docker container. Remember to set some breakpoints!<\/p>\n\n\n\n

\"Debugging<\/figure>\n\n\n\n

You should see a debugging session tab for each service. In case of issues, you can use the Services window to confirm the following items.<\/p>\n\n\n\n