Epic: Use less disk space about compose

[bfirsh]

There is also a wider discussion to have about how Docker can be more disk-friendly. Tools to clear up old containers and images would be handy regardless.

[josephpage]

+1 to clear up orphan container left after each fig build && fig up -d

[dnephin]

The main issue I've run into here is the second point. fig stop and fig rm don't remove the one_off containers created by fig run.

A -rm by defualt sounds appropriate.

[thaJeztah]

remove containers by default if they don't have volumes?

That option sounds a bit scary to me; containers without volumes may also contain information that should not be thrown away without warning.

I agree with removing the one-off containers, I think in general, those will not contain data that should be preserved, so --rm by default sounds okay.

[k4nar]

I also agree that --rm should be the default.

[kalmi]

I would argue that even --volumes could be appropriate for a software that has its focus on devenvs.

[hugochinchilla]

I also agree with --rm by default or at least an option in the yml file to toggle the behavior.

[bfirsh]

This helps a lot. #716

[dnephin]

I created this tool for doing cleanup https://github.com/yelp/docker-custodian

I think removing containers by default might be assuming too much about how compose is being used. Especially now that we have start-recreate which is able to start containers again.

@bfirsh do you think there is still work to be done here on the compose side?

[shin-]

With docker-compose down and docker system prune now, I thin we're in a good place regarding managing disk space.