Xabier de Zuazo

@estahn as always, thanks for the report :wink: Please, could you add a complete *docker-compose.yml* example, the current output and the expected output? For example, I have tried the following...

@estahn unfortunately, I do not think this can be fixed due to the way rspec and serverspec work. Right now all the containers are started, then the tests are passed,...

Yes, that's a good solution. Maybe it could be possible to implement some kind of special resource, something like a `docker_context do ... end` to isolate the different executions of...

With the original `describe` is not possible to do that. However, it does not seem possible to do it the other way either without changing the internal behavior of RSpec.

Hi @wibimaster, Thanks for the report. Can you add an example of the *Dockerfile* that fails, please.

There could be different ways to do that. What I usually do is create another Dockerfile with a long-running service that I only use for testing. See the following examples:...

Hi @wibimaster, First of all, thanks for making such a detailed report :wink: As you have deduced, the problem is that `command` executes the command in the container itself, not...

Maybe you could create multiple `Dockerspec` files for tests with different `CMD` / `ENV` instructions. See #10 for a more detailed explanation. > Check the shell opened, I didn't know...

I think this is strictly related to #8. I guess the problem is not that it is not executed, but that it is executed after the `docker_run`. The reason is...

@estahn thanks for all your reports :wink: