The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
Docker hub has significantly reduced rate limits for pulls as of 4/1, and also made unexpected changes to DA's dockerhub license.
Drupal CI is erroring due to limit - additional context + discussion in Drupal slack thread: https://drupal.slack.com/archives/CGKLP028K/p1743611728165519?thread_ts=...
Steps to reproduce
Community is reporting CI failures
Proposed resolution
We are moving CI images off of docker hub to gitlab.com registy here: https://gitlab.com/drupal-infrastructure/drupalci/drupalci-environments/...
Note: As of time of writing - we are still syncing images to new registry, will make sure it is fully populated before requesting MR.
Remaining tasks
Core's CI needs to be updated to point at new registry. I will open an MR.
Release notes snippet
Adjusted core CI image registry to use `registry.gitlab.com/drupal-infrastructure/drupalci/drupalci-environments` instead of dockerhub.
Issue fork drupal-3516954
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
compare
Comments
Comment #2
maxwhiteheadComment #3
fjgarlin commentedComment #5
fjgarlin commentedI think an alias was created somewhere from the old naming to the new naming for chromedriver.
Comment #6
fjgarlin commentedTests are passing now and code looks good. The change will be very similar for contrib.
RTBC.
Comment #12
longwaveGreen run, jobs all look OK with e.g.
Committed and pushed to all active branches to maintain parity and avoid errors in case we need to run CI against older branches.
Comment #14
andypostnew images will go to new registry, nightly tested