Michal Bultrowicz

@not-josh I see the breakages. Got a solution for that but it raises another question - I'll link the issue/PR. As for this PR in itself - I'll try to...

Issue, leading to the code fix and some thoughts - #35

Giving my 2 cents here, as I'm also having problems by not immediately seeing what went wrong in a container when a test fails. I'd be OK with just dumping...

Ok, I've made something that works perfectly for me - https://github.com/butla/pytest-docker/commit/c37ac821360a135c0cc7502c308df1f9526d02ad But my code is awful. I need to refactor. I'll try to get a PR together in the coming...

@AndreLouisCaron my solution does exactly that. I'm starting "docker-compose up" without "-d" and I'm not waiting for the output. With that, the output streams from compose will be joined with...

@AndreLouisCaron 1) Nope it was fine. Pytest would give the output from a container on failures in the proper "Output captured during tests" section. 2) I haven't. I haven't thought...

I'm not using pytest-docker at the moment, so I'll stay out of the conversation.

Can you justify why do you need this?

Ok. As I don't know when this'll be merged, maybe you can work around it by overwriting `docker_compose_file` and maybe changing the paths in your compose files?

I guess this should be reopened. I'm using Flatpak 1.7.2. Trying to enter Slack's flatpak without sudo or with `sudo -E` fails with `Can't enter user namespace: Invalid argument`. Sudo...