All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Docker Hub subscription changes
Dear Valued Customer,
We are writing to inform you that your Docker Pro subscription plan will be changing on your next invoice date on or after November 15, 2024. As part of these changes, you will now get access to all Docker products and features including: Docker Desktop, Docker Hub, and new offerings like Docker Scout and Docker Build Cloud alongside the newly integrated testing capabilities from Testcontainers Cloud.
The list price of your annual Docker Pro subscription will be updated to $9 per month, billed annually, effective on your next invoice date on or after November 15, 2024. Additionally, your annual Docker Pro subscription will be subject to our Docker Hub plan limits effective February 1, 2025.
Currently, we show that your current Docker Hub usage may cause you to exceed the Docker Hub plan limits allowed at your current plan level and consumption overages will result in additional fees. No charges on Docker Hub image pulls or storage will be incurred between November 15, 2024 and January 31, 2025.
To view your current Docker Hub usage visit the new Docker Hub Usage Dashboard
To learn how to optimize your Docker Hub usage, view our Docker Hub Optimization Documentation
For the details of this change visit our New Subscription Plans page to find the right subscription for you.
To check your next invoice date, to review, or to update your plan, please sign in to your account and click on the billing page for details.
If you have any questions, you can view the blog, New Subscription Plan page with FAQ, or contact the customer support team.
Thank you for choosing Docker. We remain dedicated to providing you with the quality and service you deserve.
Thank you,
The Docker Team
Interestingly I'm a a member of 3 teams and the contact for 1 pro account. All Teams and my Pro account are "Currently, we show that your current Docker Hub usage may cause you to exceed the Docker Hub plan limits allowed at your current plan level" so seems like it might go up even more than the ~40% (for pro).
I'm guessing the storage limit is going to be rather small. Too small for those managing larger systems and thats most people using Docker professionally.
Currently there isnt a way to work this out, and there doesnt appear to be any published information on this.
Some of my clients will move to Github Packages over this I expect. Docker Hub's overly expensive seats have always been a good tradeoff for the resource costs of github packages (for probably all but the largest employers / high seat count)
Comments
Thank you for paying for my free account
At-least its a business expense!
Damn ,we were storing a lot ( think TBs worth of docker images ) with no cleanup script because hey it's unlimited , but will need to create a cleanup job now , if only https://goharbor.io/ was not so complicated to setup
I dont think myself or anyone I work for is storing unnecessary amounts. Probably a TB over a 200 odd projects (a few projects would be 20 x ~1GB but most are only 300MB or so and rarely updated).
DockerHub ages out old inactive images already. Unless you are frequently updating your images you are probably using less than you think.
This explains why they want to change how storage is billed
@SplitIce when does your sub expire btw , are they atleast honoring , your current plan till end of billing period , or will they start charging based on usage , even if you have not subscribed to new plan ?
On my pro account "Due Oct 24, 2024", its yearly.
so they will start charging everyone for usage from jan , will need to move , but they still seem to be not charging for bandwidth , so I guess , they will still be cheaper ,
Storage with the likes of GitHub tends to be more expensive from what I have seen.
If you are caching your images locally (e.g Kubernetes pull IfNotPresent) then you shouldnt be burning too much bandwidth in your deployment.
Our biggest users is actually CI, some of those jobs use multiple containers and are usually run from a fresh environment (sometimes itself another container)