compose_run_options: [rm] ???

[bibendi]

compose_run_options: [rm] ???

[bibendi]

Hi!

You have described the behavior that Dip is using by default. You don't need to do anything to achieve this.

You can inspect commands that Dip is sending to Docker Compose by writing something like below:

DIP_ENV=debug dip <cmd>

[LimeBlast]

So it is, my apologies. I think it was RubyMine spinning up all the extra containers, and I assumed it was dip.

I know this is a bit off topic (so I'm happy to close this ticket). but have you had much luck running dip commands with/via RubyMine?

Thanks.

[bibendi]

I've been coding with RubyMine for a while, but I prefer using the console to run application's commands. I just set up a remote interpreter to allow RubyMine downloading gems from Docker.

[LimeBlast]

That sounds pretty similar to what I've been doing, and it seems to work fairly well - although I've not figured out how to get debugging to work.

In any case, thank you for your help :)

[bibendi]

I don't use RubyMine's debugger as well :)
I just type binding.pry in a code file and start an application.