Remote Docker Resource Class
complete
K
Keith Gonyon
It seems right now that you can't specify a resource class for the remote docker environment. It would be nice to either use the resource class from your primary image or be able to specify one in the setup_remote_docker command. We were using a docker with remote docker to build, but the build times were too slow so we switched to machine for the time being.
B
Ben Limmer
Thanks Sebastian. The documentation linked from your link, https://circleci.com/docs/building-docker-images/#specifications, still references a static, remote docker instance. Is the documentation out of date? Is there an official release blog/notes/etc I can reference to understand how this is resolved?
S
Sebastian Lerner
Ben Limmer: That docs page is in the process of being updated. Until the docs are updated, the new architecture is effectively the equivalent of a machine executor. Some details in here: https://discuss.circleci.com/t/changes-to-remote-docker-reporting-pricing/47759
So now the virtual machine that is being used will be the same size as specified in the "resource_class:" key in your config.yml for that job.
B
Ben Limmer
Sebastian Lerner: Sounds good - this new approach makes more sense, anyway. Is there any way to opt-in to the new behavior before June 15?
S
Sebastian Lerner
Ben Limmer: Projects have been gradually migrated to using this new architecture over the past 6 months. As of April 7, all projects are using the new architecture. https://discuss.circleci.com/t/setup-remote-docker-architecture-change-phase-2-jobs-that-use-docker-layer-caching/47083/3?u=sebastian-lerner
On June 15, the reporting & pricing will change. But the underlying architecture has already changed.
S
Sebastian Lerner
complete
this is now complete https://discuss.circleci.com/t/setup-remote-docker-architecture-change/45303
S
Sebastian Lerner
under review
We're currently re-evaluating the architecture for Remote Docker. We're looking at this request as part of the re-evaluation
Ricardo Feliciano
This would allow the ability to enable ARM builds this way.
E
Eddie
Customers expressed interest in this as means to enable GPU exposure on docker builds.