Erica Kastner

Because the `restart` flag wreaks havoc when you try to `docker-compose run` it*, I'm wondering if our generated docker-compose.yml should just always include 2 versions of each service -- a...

`docker rm` has different behavior than a stop. A stop stops the running container, leaving the stopped container in an inspectable state. An rm deletes the container after stopping.

@seamusabshere First, what we're doing here with a shared test configuration is not something docker-compose refuses to upstream. There are other features cage provides where that is the case. Second,...

In fact, I'd even go so far as to argue that we no longer _need_ `cage test `, even for our use case.

In the end, I'd rather just have a bare `cage test` command that runs acceptance tests and that's it.

That sounds good. The minimum docker version for compose 2.1 is v1.12.0, which is almost 2 years old now.

Hi @camjackson normally private registries are supported, but if I had to guess it's likely that the port number or hierarchical org-name/app-name is throwing off cage. We'll take a look...

It might be nice to be able to generate Dockerfile, docker-compose.yml, and maybe CI and dev scripts. For instance, if you have a global placeholder postgres database, you might want...

...aaaand looks like I need to fix the mount check :(

OK, fixed mounted check