![]() The bottom line is, we need our Docker container to be reachable by an external debugger. Its very similar to the tutorial involving Docker Compose but without the nginx reverse proxy. To easily get up and running, you can use this Github repository to get up and running. If you’re coming directly to this tutorial on debugging docker containers, I’ll be assuming you’re familiar with Docker Compose.Īs a bonus, we’re also going to look at nodemon for monitoring server side changes and restarting our server without us having to shutdown and restart containers on ever server-side change. If you haven’t started, but are interested in hosting your applications development environment inside Docker containers, you’re going to want to check out the recently released Docker for Devs tutorial. In this first part were going to look at how to use WebStorm, followed by Visual Studio Code and finally hooking up the good Ol’ fashion node.js debugger. This is the first of a three part series where were going to look at how to debug docker containers running an React.js/Node.js/Express.js application. Go to C:\Users\\.path\ and all your toolbox installed applications should be there.If you’re using Docker to host your applications development environment, it will be important to know how to debug your applications source code running in the container.Click on Ok in Edit environment variable > Environment Variables > System Properties.Click on new and paste your path there. ![]()
0 Comments
Leave a Reply. |