Peter

I have/had a working chart ( https://github.com/baez90/kube-ingress-aws-controller-helm ). I didn't use it for a while so it is "completely" outdated and I'm pretty sure that there are a lot of...

I'm actually wondering why not directly 'including' upstream `docker-compose` as version 2 is implemented in Go. I had a 'quick look' how hard it would be and I think it's...

@mdelapenya I know you're not going to like this but: how about another breaking change/deprecating the `DockerCompose` interface? :smile: The current interface: ```go type DockerCompose interface { Down() ExecError Up()...

1. I'm not sure if we actually need to support **all** commands `docker-compose` supports. From my perspective `up`, `down` and optionally `run` would suffice at least for the beginning. 2....

I'm aware that the current API isn't compatible with my proposal (even though it could be adopted for the time being) but we released breaking changes earlier and I think...

I wouldn't mind to work on this together? I'd like to wait what the `docker-compose` guys are going to tell us regarding using it as a library and depending on...

It appears so far neither of the approaches guarantees a stable API of `docker/compose`. While this isn't ideal I don't think this is a reason to dump the idea completely...

To improve further discussions I created a WIP PR containing the API based implementation I've been working on. I also duplicated the old test suite and adopted it for the...

Fine for me if there's more to discuss?

Have a look at the `TestContainerAttachedToNewNetwork` test in `docker_test.go` it already 'covers' what you are trying to avoid. I think it has something to do with whether a container is...