Dylan Hardison [:dylan] (he/him) Assignee
	Description • 7 years ago

As part of the cloudops migration, BMO needs a CircleCI configuration that builds a docker image for {master,development,production} branches.

	Dylan Hardison [:dylan] (he/him) Assignee
	Comment 1 • 7 years ago

Reading through https://circleci.com/docs/2.0/ it seems like the "image" I specify when using this
could just be anything, as I literally don't care what the executer docker container is, as all my code runs in the docker container that is built from the repo, right?

This is with providing a 'setup_remote_docker' step, of course: https://circleci.com/docs/2.0/building-docker-images/

	Chris Kolosiwsky [:ckolos] (ckolos has left the building)
	Comment 2 • 7 years ago

You should use the centos:6 image for your docker container. It's immaterial which container circle builds with (until it isn't, of course, but we're not there yet :) )

	Dylan Hardison [:dylan] (he/him) Assignee
	Comment 3 • 7 years ago

(In reply to Chris Kolosiwsky [:ckolos] from comment #2)
> You should use the centos:6 image for your docker container. It's immaterial
> which container circle builds with (until it isn't, of course, but we're not
> there yet :) )

my image is already built. Or that is, it is already centos:6 and I think you've confirmed my question. Thanks!

	Ed Morley [:emorley]
	Comment 5 • 7 years ago

Out of curiosity, why CircleCI and not Travis?

	Chris Kolosiwsky [:ckolos] (ckolos has left the building)
	Comment 6 • 7 years ago

In cloudops, CircleCI is used to automate the docker build/push process.