Time to Bail · Boarding pass
Yes.
Autobuilds retire April 1, 2027. Copy your build rules into GitHub Actions or Bitbucket Pipelines first.[1]
Bail means: it is ending, or getting much worse, for this group. Leave before the date.
Docker Hub Automated Builds are retired April 1, 2027
Docker Hub Automated Builds (Autobuilds) are deprecated and fully retire on April 1, 2027. Docker's guide moves these builds to GitHub Actions or Bitbucket Pipelines. You can only see the build settings in the Docker Hub web page, so copy them first.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
Tick steps as you go. Your progress stays in this browser.
In Docker Hub, open Builds, then Configure automated builds. Note the rules and variables.
Create a token that can push to the repository and save it as a CI secret.
Build and push the same tags from GitHub Actions or Bitbucket Pipelines.
Put what hooks/build or hooks/post_push did into the workflow steps.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
| Fully retired | April 1, 2027[1] |
|---|---|
| Deprecation notice | May 6, 2026[3] |
| Docker's migration guides | GitHub Actions and Bitbucket Pipelines[1] |
| Where your settings are | Only in the Docker Hub web page: Builds tab, Configure automated builds[1] |
| What to copy | Source repository, Autotest, build rules and build environment variables[1] |
| Access for CI | A Personal Access Token with Read & Write, or an Organization Access Token with pull and push rights[1] |
| Who has Autobuilds | Docker Pro, Team or Business subscriptions[2] |
| Hook files that only Autobuilds run | hooks/build, hooks/test, hooks/push and the pre_ and post_ hooks[2] |
| Repositories with Autobuilds | Stop building on Docker Hub after April 1, 2027[1] |
Check it yourself. Every fact above links here.
Time to bail on Docker Hub Automated Builds (Autobuilds)? Yes. Autobuilds retire April 1, 2027. Copy your build rules into GitHub Actions or Bitbucket Pipelines first.
On our scale this is Bail: it is ending, or getting much worse, for this group. Move your work out now.
Docker Hub Automated Builds (Autobuilds) are deprecated and fully retire on April 1, 2027. Docker's guide moves these builds to GitHub Actions or Bitbucket Pipelines. You can only see the build settings in the Docker Hub web page, so copy them first.
Here are the facts we checked:
This is a full shutdown, not a pause. When the service closes, files and lists you did not save may be gone.
Do not wait for a last reminder email. Those emails are often late, and some never come.
Docker is the main source for this page. Docker has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Repositories with Autobuilds: Stop building on Docker Hub after April 1, 2027.
Export takes some work. Do not leave it for the last day.
The date to remember is April 1, 2027. After that, it may be too late to save what you need.
A few rules help every move go well:
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.
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.
No questions collected yet.
Thanks.
Run SaaS spend at work? Get these changes before the invoice
Arrivals · for builders
People leaving Docker Hub Automated Builds (Autobuilds) need a new home. Get the playbook for this change, and list your product here.
Listing is free. An editor checks it. Not ranked. Not paid.
One email when we publish a checked change in the category you pick. No account needed.
One email on Mondays: the gates in the next 14 days, with the first step for each.