ConceptsResource limits
What Ferry does not limit
Builds, disk space, I/O and the network have no limit.
A resource limit covers memory, CPU, processes and logs. Ferry sets no limit on four other things.
The four things with no limit
| No limit on | What it means |
|---|---|
| Builds | docker build runs in BuildKit. BuildKit has no limit of memory or CPU for one build. A build can use all the memory and CPU of the server. |
| Disk space | Volumes, the filesystems of containers, images and the build cache have no quota. |
| Disk and network I/O | Ferry sets no limit on I/O or on bandwidth. |
| The network | All services and datastores share one private network. Each container can reach each other container by its name. |
What you can do
docker image prune
docker builder pruneThese commands remove the images and the build cache that Docker does not use.
--build-concurrency(default 2) limits the number of builds at the same time.- The free-disk check runs before a build, not during the build. It stops only new deploys and new datastores.
--keep-imageslimits the images that Ferry made. You must remove the other images.- Only its password protects a datastore on the private network.
The volumes with no quota are the volumes of datastores and the disks of services.
Ferry does not make sure that all the limits together fit on the server. See When the server has no free memory.