CircleCI Ideas

Resource Class for Remote_Docker and Machine executor

Currently for building Docker images there are no options to increase resource_class as the machine executor and remote docker environment share the same specs at 2 cores and 8Gb of ram.

This is a request to extend the resource class feature to all executors. (MacOS has a current post already for this issue).

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Nov 28 2018
  • Taking votes
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    17 Apr 05:52

    +1 for this

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    25 Apr 22:08

    +1

  • Admin
    George Reyes commented
    30 Apr 17:28

    We understand the value of giving our customers more control over the resources their remote_docker and machine jobs are using. Right now only one resource size for both remote_docker and machine is available, but we will consider expanding our offering here in the future.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    30 Apr 17:34

    George what do you mean by  resource size ?
    where is the documentation for that?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    06 May 20:19

    +1 yes please, we are spinning up several containers during our circleci integration test job

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    28 May 18:33

    Another +1 for this.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    06 Jun 20:34

    Following up on the question about documentation, here are the links to current resources sizes:

    remote_docker: https://circleci.com/docs/2.0/building-docker-images/#specifications

    machine: https://circleci.com/docs/2.0/executor-types/#using-machine

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    10 Jun 20:37

    This is a full blocker for bringing our large open source project to CircleCI. We have a mandate to run tests on VM's and not in containers. We were in the process of beginning migration to CircleCI, but this will prevent us from doing so. Is there any hope for this in the near future? We are about to choose our next-gen platform for CI and will be vendor locked in once we do. As it stands now, this can't be CircleCI, despite my overwhelming want to make the recommendation to our Technical Steering Commitee

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    24 Jun 16:48

    My company is on a CircleCI performance plan and we're stuck with the small specs of the machine executor. It's a real blocker for us. We'll have to move to another CI provider next month if the resource_class feature available for docker containers is not made available to machine executors too.

    Can you share your timeline for this feature?

    Thanks.