Architecture Change: Setup_remote_docker

Overview

CircleCI is making changes to the underlying architecture of how the setup_remote_docker feature works on our platform.

  • From within your job, if you are using the Docker CLI or SDK (set to read the configuration of the Docker client from the environment) -  no changes are required.
  • If you have a custom script that refers to the Docker environment variables DOCKER_TLS_VERIFY or DOCKER_CERT_PATH - these will no longer be set.
    In the new architecture, the Docker daemon is available on the standard UNIX socket, and TLS certificates are no longer required.

 

User Impact

  • The new architecture should result in faster job execution for the vast majority of users who use setup_remote_docker.
  • The architecture is significantly simplified and should improve the reliability of jobs that use setup_remote_docker.


Recommended Docker Versions

If your projects use the following docker versions, CircleCI recommends using the default version since it is now being kept up to date :


docker-17.03.0-ce
docker-17.05.0-ce
docker-17.06.0-ce
docker-17.07.0-ce
docker-17.09.0-ce
docker-17.11.0-ce
docker-17.12.1-ce
docker-18.03.0-ce
docker-18.03.1-ce
docker-18.05.0-ce
docker-18.06.0-ce
docker-18.09.3
docker-19.03.8
docker-19.03.12
docker-19.03.13
docker-19.03.14
docker-20.10.2
docker-20.10.6
docker-20.10.7
docker-20.10.11
docker-20.10.12

This is to avoid a possible risk of incompatibility with the more current software on the new architecture and the older version of Docker being specified in the job’s configuration file.

 

Exclusions

At the moment, this rollout excludes jobs that use DLC in tandem with setup_remote_docker. Those jobs will be included in the rollout at a later date.

 

If you are seeing issues with jobs that use the setup_remote_docker feature, please submit a support ticket at https://support.circleci.com/

 

Additional Resources:

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.