Docker Community Forums

Share and learn in the Docker community.

Automated Build resource restrictions


(Steven Edwards) #1

Is there a list of the resource limits placed on Automated Builds?

As an example, I ran into an excruciating two-hour (user time, I think) build limit yesterday when attempting to build HHVM on CentOS7 from source; success finally arrived with make -j2 after a few make and make -j5 failures.


Error pushing to registry: no space left on device
(Andy Rothfusz) #2

The current limits on Automated Builds are:

  • 2 hours
  • 2 GB RAM
  • 1 CPU
  • 30 GB Disk Space

For larger builds you should either break them into several Automated Builds connected by FROM statements and Repository Links, or build them locally on your machine and push them.

Please remember that the Automated Builds are a free service offered to the Docker community and try to work within the constraints provided so that we can share these resources with more people.

[Edited to add Disk Space quota]


(Steven Edwards) #3

Thak you for the information, Andy.

I will keep these limits in mind for future builds.