Alternative to using remote docker host for building & executing docker containers
Building and testing docker containers in CircleCi is a little awkward and execution times are long due to the need to spin up a second remote image to run/test Docker images.
The remote docker executor is one way to work around not being able to run a Docker container from CI Docker container.
At the end of the following article, a solution is described that may allow the target Docker images to be run as siblings containers on the CI instance. If this is possible it would eliminate the need to spin up a remote docker executor instance to run/test a target container.