timetobail
My stack

GitLab · Forced move · Tracked since October 17, 2026 · Sources checked Oct 17

Time to bail on GitLab Runner on the docker+machine executor?

Time to Bail · Boarding pass

FromGitLab Runner on the docker+machine executor
ToYour pick

Act. You can stay.

The executor is removed in GitLab 20.0, planned for May 20, 2027. Move to GitLab Runner Autoscaler first.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
GitLab 20.0 release (planned)
Time left
214days
Status
Act

GitLab 20.0 removes the Docker Machine executor (May 20, 2027)

GitLab Runner's Docker Machine executor has been deprecated since GitLab 17.5. GitLab plans to remove it in GitLab 20.0. That release is planned for May 20, 2027. Use GitLab Runner Autoscaler instead. It has plugins for AWS EC2, Google Compute Engine and Azure VMs.

Email me 7 days before May 20

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

What to do before May 20

Tick steps as you go. Your progress stays in this browser.

  1. Find your autoscaling runners

    Look for executor = "docker+machine" in each runner config.toml.

  2. Set up the Autoscaler

    Install GitLab Runner Autoscaler with the AWS, Google or Azure plugin.

  3. Move jobs and test

    Give the new runners the same tags. Run a few pipelines. Then turn off the old runners.

Email me 7 days before May 20

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

Facts we checked

Facts and their sources
GitLab 20.0 release (planned)May 20, 2027[2]
Removed inGitLab 20.0[1]
Deprecated inGitLab 17.5[1]
Until thenNo new features; GitLab no longer fixes newly found bugs in its Docker Machine fork[1]
ReplacementGitLab Runner Autoscaler, with plugins for AWS EC2, Google Compute Engine and Azure VMs[1]
Executor name in runner configdocker+machine[3]
GitLab.comDeprecated features can be removed at any time in the month before the release[1]
Runners on docker+machineLose the executor in GitLab 20.0[1]

Sources

Check it yourself. Every fact above links here.

  1. Deprecations and removals by version GitLab · primary · checked Oct 17
  2. GitLab release and maintenance policy GitLab · primary · checked Oct 17
  3. Install and register GitLab Runner for autoscaling with Docker Machine GitLab · primary · checked Oct 17
Read the published editorial report

What changed

Time to bail on GitLab Runner on the docker+machine executor? Act. You can stay. The executor is removed in GitLab 20.0, planned for May 20, 2027. Move to GitLab Runner Autoscaler first.

On our scale this is Act: change a setting or plan before the date. You can stay.

GitLab Runner's Docker Machine executor has been deprecated since GitLab 17.5. GitLab plans to remove it in GitLab 20.0. That release is planned for May 20, 2027. Use GitLab Runner Autoscaler instead. It has plugins for AWS EC2, Google Compute Engine and Azure VMs.

Here are the facts we checked:

  • GitLab 20.0 release (planned): May 20, 2027 (GitLab)
  • Removed in: GitLab 20.0 (GitLab)
  • Deprecated in: GitLab 17.5 (GitLab)
  • Until then: No new features; GitLab no longer fixes newly found bugs in its Docker Machine fork (GitLab)
  • Replacement: GitLab Runner Autoscaler, with plugins for AWS EC2, Google Compute Engine and Azure VMs (GitLab)
  • Executor name in runner config: docker+machine (GitLab)
  • GitLab.com: Deprecated features can be removed at any time in the month before the release (GitLab)
  • Runners on docker+machine: Lose the executor in GitLab 20.0 (GitLab)

You can stay on GitLab. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

GitLab is the main source for this page. GitLab has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Runners on docker+machine: Lose the executor in GitLab 20.0.

The date to remember is May 20, 2027. Make the change before then.

What to do before May 20

  1. Find your autoscaling runners. Look for executor = "docker+machine" in each runner config.toml.
  2. Set up the Autoscaler. Install GitLab Runner Autoscaler with the AWS, Google or Azure plugin.
  3. Move jobs and test. Give the new runners the same tags. Run a few pipelines. Then turn off the old runners.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on GitLab Runner on the docker+machine executor can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product