RubyMine cannot find Gem binaries for Docker Compose remote

I found the solution!!

In my Dockerfile I had:

# Configure an entry point, so we don't need to specify 
# "bundle exec" for each of our commands.
ENTRYPOINT ["bundle", "exec"]

That allowed me to do 

rails server -p 3000 -b '0.0.0.0'

to start the server, but broke Rubymine. Now, I removed the entryPoint in my Dockerfile and changed the command for my app to:

command: bundle exec rails server -p 3000 -b '0.0.0.0'

..and I am able to add my Docker Compose as a remote!! :D 

@Dfediuk, thanks for your suggestion anyways! However, for me it did not work unfortunately.

I have found the solution!
«If you are configuring a remote interpreter using rbenv version manager, you have to specify ruby executable located under the directory versions, rather than shims».

Hello, 

Thanks a lot for your investigation, somehow this option influenced on our integration with Docker. So we need also investigate here. But for sure this is a bug, please vote https://youtrack.jetbrains.com/issue/RUBY-20710.

You could create custom docker-compose.dev.yml file with the only service named as the target service from original docker-compose.yml and set its entrypoint to an empty list;

Then add docker-compose.dev.yml after original docker-compose.yml when adding Remote Ruby Interpreter

In this case every run from terminal will be with entrypoint from docker-compose.yml. And Rubymine will be able to run any command in your container.