Lachlan Donald

We've brought back `EnableDockerUserNamespaceRemap` in #410. You can use this in https://s3.amazonaws.com/buildkite-aws-stack/master/aws-stack.json and we'll be cutting a 3.1.0 release soon.

I'm going to re-open this one, as it's still an issue when user namespace remapping is turned on.

Yup, still an issue @pda.

Sorry for the delay responding @KevinGrandon. I like the suggestion of the top-level logs block!

Currently we capture logs of dependant services as artifacts on failure, is this not adequate @KevinGrandon? The more I look at this, the gnarlier it is to implement.

> Maybe just an option to background tail all logs before execution? I'll look into this, but the issues is that `docker-compose run` creates ephemeral services that can't easily be...

Also `docker-compose logs` and `docker logs` will exit if the containers or services aren't running yet.

Sorry about this @uriahcarpenter, we'll get some tests in place to catch this regression.

I've suspected a race condition for container logs for a while. We'll investigate.

Yeah, I think this would be worth adding a stack parameter for.