Docker Terms of Service Change

"The updated Docker Terms of Services will take effect immediately. If you continue to use our products and services, you are agreeing to the updated Docker Terms of Service.

Related to this update, Docker is introducing a container image retention policy which will be enforced starting November 1, 2020. The container image retention policy will apply to the following plans:

* Free plans will have a 6 month image retention limit
* Pro and Team plans will have unlimited image retention"


6 thoughts on “Docker Terms of Service Change”

  1. Sounds like this only applies to ‘inactive’ images, ones that haven’t been fetched in 6mo.

    However this might mean old or low activity images for popular OSS projects might disappear.

  2. Essentialy pruning 4.5pb of inactive images. Common sense I would say which saves them a few bucks while hopefully getting rid of old insecure containers.

    What is a container image retention limit and how does it affect my account?

    Image retention is based on the activity of each individual image stored within a user account. If an image has not either been pulled or pushed in the amount of time specified in your subscription plan, the image will be tagged “inactive.” Any images that are tagged as “inactive” will be scheduled for deletion. Only accounts that are on the Free individual or organization plans will be subject to image retention limits. A new dashboard will also be available in Docker Hub that offers the ability to view the status of all of your container images

    Why is Docker introducing an “inactive” image policy?

    As the world’s largest repository of container images, Docker Hub stores more than 15PB of data. After detailed analysis of the container images stored on Docker Hub, we found that 4.5PB of the data have not been pushed or pulled within 6 months or longer. We are making this move to optimize operations and make the Docker Hub service even stronger for developers and development teams around the world who are using the service to build and ship applications.

  3. The policy doesn’t say, but I’m hoping they send email notification when an image goes inactive.

    I recently threw like 20 images up there, all projects from my various books. I thought it might be nice for readers (or non-readers) to be able to spin them up with a single command. I can’t imagine they’ll ever be high-volume images, and I wouldn’t be shocked if they went inactive. And that’s fine, since basically I could just go pull them and voila, re-active. But if I need to go check them every 6 months, that’s a bit of a pain. An email would be a nice reminder.

    Not a big deal I guess, and I have no issue with the policy… just hoping for a small convenience is all.

    EDIT: Ignore the silly man, as was pointed out in comments below, the policy DOES address exactly this, I just somehow managed to completely miss it. My bad, brainfart.

  4. Anyone know how legacy, paid “Micro” plans will be affected? I currently have an organization that pays the $7/month for 5 private repositories and 5 parallel builds.


Leave a Comment