Our project has a docker setup configured using a set of docker-compose.yml files. I haven’t put it in DockerHub yet, and I’m not 100% sure if I should (super new to Docker).
I don’t think I want to publish it, though, which means that I either have to use the remote docker environment (and work around the lack of volume support) or I have to use the machine executor (which will be slower to start, and possibly cost more in the future). This doesn’t seem like a great user experience – either I use a VM and throw away Circle’s sweet Docker integration, or I hack up my Docker config to be Circle-friendly, which seems to defeat the point of Docker.
Am I missing something here? Is there an easier way to do what I’m trying to do? Or perhaps there’s some way that everything private and sensitive can be kept out of the docker image, allowing it to be published?