Early Access Program News

RubyMine 2017.2 EAP 5: Debugging Docker Compose apps

RubyMine 2017.2 EAP 5 (build 172.2953.21) has been released. For this EAP we’re providing long-awaited support for debugging apps inside of a docker-compose service. If you haven’t configured Docker Compose in RubyMine yet, refer to this post and set it up in minutes. Here’s how you can try the debugger:

Open your Docker project in RubyMine, and make sure you’ve chosen Docker as a remote SDK in Preferences / Settings | Ruby SDK & Gems:


Next, add gem ‘ruby-debug-ide’ and gem ‘debase’ to your Gemfile, as they are required to make the RubyMine debugger work. Don’t forget to run docker-compose build to install the gems to your project:


Run docker ps to make sure your web app isn’t currently running. If it is, stop the container:


Now you are ready to try debugging your container.

Choose a file to debug and set breakpoint(s) where needed. Then start the debugging session for the development environment:


That’s it!

Note that since this is an Early Access Program, many things may be imperfect. If you face any issues while trying out this new feature, please provide your feedback in the related issue.

In other improvements, this update also features Javascript enhancements and fixes a number of bugs.

Download this EAP from our website.

See the release notes for the full list of improvements. Let us know your thoughts in the comments, and join us on Slack.


Your RubyMine team

Comments below can no longer be edited.

4 Responses to RubyMine 2017.2 EAP 5: Debugging Docker Compose apps

  1. Avatar

    JP says:

    December 8, 2018

    Hello there, I tried this out. I am currently using Rubymine 2018.3 on Windows and also on a Mac. I am able configure following your instructions. When I click on debug, my container is started and I am able to see there there’s a container running by typing ‘docker ps’ into the terminal. However, I am not able to access the web application (Ruby On Rails) by entering into the browser. I also tried entering my docker machine ip and that doesn’t seem to work either. Am I missing something?

    • Avatar

      Andrey Vokin says:

      December 10, 2018

      Could you try to access by localhost:3000 or (I remember this issue when I worked with Docker on Windows)

  2. Avatar

    henil says:

    August 23, 2019


    I am running the rails on port 3005. but the debugger tries to load at 3000, what do I do? Also, if change the url to localhost:3005, it doesn’t stop at breakpoints. How do I fix this?

    • Avatar

      Olga Kuvardina says:

      September 5, 2019

      could you please specify which run configuration you’re launching? If it’s Rails one then you can specify a necessary port there.

Discover more