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

3 Reply templates

Answer the question first. Link only if it helps. Always keep the disclosure line. Never post the same text twice.

Helpful first

Sorry you have to deal with this. You can stay on GitLab. Here is what to change before May 20, 2027:

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.

If they would rather leave, describe a verified way <your product> can help: <your link>
[Disclosure: I build <your product>.]

Short answer

You have until May 20, 2027. You can stay on GitLab. First: find your autoscaling runners. Then set up the Autoscaler.
Happy to help if you get stuck.
[Disclosure: I build <your product>.]

4 Switch-page builder

Create a draft “Switch from GitLab” page. Add your product, review every claim, then copy HTML or Markdown. Your product claims need your own evidence.

Add your product name to replace “Your product”.

Preview

Switch from GitLab to Your product

GitLab Runner on the docker+machine executor: a change is due by May 20. You can stay on GitLab. If you would rather leave, here is how to move to Your product.

What changes at GitLab

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.

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 if you make the change. This page is for people who would rather leave.

What Your product gives you

Write two or three short lines here. Say what Your product does, who it is for, and what it costs. Use only facts you can show.

How to move from GitLab to Your product

Save what you need from GitLab. Keep a copy before you cancel anything.
Import into Your product. Say which files you accept and how long an import takes.

Tell readers the key date: May 20, 2027.

Questions people ask

If Your product has a direct answer to one of these, add it here. Keep it short and true.

How to help new users settle in

Send one short email. Say what changed, where to find you now, and what they need to do. 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.

Sources

Deprecations and removals by version — GitLab (primary), checked 2026-10-17
GitLab release and maintenance policy — GitLab (primary), checked 2026-10-17
Install and register GitLab Runner for autoscaling with Docker Machine — GitLab (primary), checked 2026-10-17

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

1 Related discussions

2 What people ask