I’m slightly confused about the way that
setup_remote_docker interacts with the primary container listed in the config.yml.
Does primary container type really matter only very little in this world?
For example, in https://circleci.com/docs/2.0/building-docker-images/, we are defining the primary container to be
golang:1.6.4, then calling
This seems to mean “Put the
golang:1.6.4 into the remote area” (I still don’t understand why this is even necessary… I guess its just some technical issue of CircleCI we don’t have context on?), then install Docker again within THAT Docker instance (Begs the question: is there just some docker image configured for this already so we can skip that step and list that as our primary container?). Now run
docker build using your own
Dockerfile in your repo. Any commands like
run: docker mybuildname exec bundle install actually execute this newly built docker container within your primary docker container. Now push that newly-built docker container.
From the outside, this all just seems over-complicated… seems like there’s no benefit to using anything other than a plain
ubuntu package as your primary container in this setup, assuming you want to run all the commands in the docker container that you are building with
Dockerfile, and not the primary container.