Compose.ng: Removed Container Remains

[B1ue-W01f]

I believe currently, a container previously deployed through compose.ng, having been removed from the compose.ng pillar is not deleted but stays running on the host until removed manually. Should this be the correct workflow?

I would expect, not from a docker way of working as such but a saltstack / declarative way of working, that containers removed from the compose should be purged - or able to be enabled / disabled.

[noelmcloughlin]

#300