Playbook: Docker Hub Automated Builds are retired April 1, 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. Docker Hub Automated Builds (Autobuilds) closes on April 1, 2027. Save what you can first:

1. Copy your build settings. In Docker Hub, open Builds, then Configure automated builds. Note the rules and variables.
2. Make an access token. Create a token that can push to the repository and save it as a CI secret.
3. Write the CI workflow. Build and push the same tags from GitHub Actions or Bitbucket Pipelines.

To replace Docker Hub Automated Builds (Autobuilds), describe a verified way <your product> can help: <your link>
[Disclosure: I build <your product>.]

Short answer

Docker Hub Automated Builds (Autobuilds) closes on April 1, 2027. Save what you can first: copy your build settings. Then make an access token.
Happy to help if you get stuck with the move.
[Disclosure: I build <your product>.]

4 Switch-page builder

Create a draft “Switch from Docker Hub Automated Builds” 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 Docker Hub Automated Builds to Your product

Docker Hub Automated Builds (Autobuilds) closes on April 1. Here is how to save what you can and move to Your product.

What closes at Docker

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.

Fully retired: April 1, 2027 (Docker)
Deprecation notice: May 6, 2026 (Docker)
Docker's migration guides: GitHub Actions and Bitbucket Pipelines (Docker)
Where your settings are: Only in the Docker Hub web page: Builds tab, Configure automated builds (Docker)
What to copy: Source repository, Autotest, build rules and build environment variables (Docker)
Access for CI: A Personal Access Token with Read & Write, or an Organization Access Token with pull and push rights (Docker)
Who has Autobuilds: Docker Pro, Team or Business subscriptions (Docker)
Hook files that only Autobuilds run: hooks/build, hooks/test, hooks/push and the pre_ and post_ hooks (Docker)
Repositories with Autobuilds: Stop building on Docker Hub after April 1, 2027 (Docker)

This is a full shutdown, not a pause. When the service closes, files and lists you did not save may be gone.

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 Docker Hub Automated Builds to Your product

Copy your build settings. In Docker Hub, open Builds, then Configure automated builds. Note the rules and variables.
Make an access token. Create a token that can push to the repository and save it as a CI secret.
Write the CI workflow. Build and push the same tags from GitHub Actions or Bitbucket Pipelines.
Move hook logic. Put what hooks/build or hooks/post_push did into the workflow steps.
Import into Your product. Say which files you accept and how long an import takes.

Tell readers the key date: April 1, 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

Migrate from Autobuilds — Docker (primary), checked 2026-10-17
Advanced options for autobuild and autotest — Docker (primary), checked 2026-10-17
Docker Hub release notes — Docker (primary), checked 2026-10-17

Docker Hub Automated Builds are retired April 1, 2027

1 Related discussions

2 What leavers ask