Run command in existing container about dip

[bibendi]

Hi!

it starts a new container each time, so startup is slow. How can I use an existing container if I run docker-compose up beforehand?

You can't reuse it. This architecture is by design. The startup can't be slow, because the overhead of starting a new container tends to zero.

You can find good working examples at:

• https://github.com/evilmartians/terraforming-rails/tree/master/examples/dockerdev
• https://github.com/bibendi/dip-example-rails

[vitobotta]

Hi @bibendi, it's weird but if I run tests from inside the existing container it's a bit faster than if I run them through the dip command (my config is correct). Could it be because on Mac Docker uses a virtual machine behind the scenes? Thanks

[bibendi]

Probably yes.

I have that numbers on my Linux machine:

$ time dip run bash -c exit

0,76s user 0,10s system

Overhead is only about 0,76s, so it is no bother me.

[vitobotta]

Uhm. I ran that command and I get

dip run bash -c exit 0.55s user 0.15s system 31% cpu 2.194 total

so it's not bad I guess. Perhaps I am complaining too much 🗡

Thanks!