FerryDocs
ConceptsResource limits

Server defaults

A service or a datastore with no limit of its own gets the defaults of the server.

Edit on GitHub

Own limit. The limit that you set on the service or the datastore.

1 / 2
Ferry uses the first value that it finds

Change the defaults

Start ferryd with the , or with their .

Terminal
ferryd --default-memory-limit 1G --default-cpu-limit 2
FERRY_DEFAULT_MEMORY_LIMIT=1G FERRY_DEFAULT_CPU_LIMIT=2 ferryd   # the same
Flag of ferrydDefaultWith 0
--default-memory-limit512 MiBNo memory limit for a container with no limit of its own
--default-cpu-limit1 CPUNo CPU limit for a container with no limit of its own
--pids-limit1024The guard is off
--log-max-size10 MiBThe guard is off
--log-max-files3
--min-free-disk1 GiBThe guard is off

The flags accept the sizes of the memory limit and the amounts of the CPU limit. Server options lists each flag.

See the defaults

ferryd prints them when it starts.

ferryd output (excerpt)
  Docker          : 28.3.3 (8 CPUs, 7.7 GiB)
  Data            : ./ferry-data
  Limits          : 512 MiB / 1 CPU per container (default), 1024 pids, logs rotated at 10 MiB × 3
  Free disk check : deploys need 1 GiB free

ferry info and the Server page of the dashboard show the defaults and the size of the .

ferry info (excerpt)
Default limits:  512 MiB memory, 1 CPU per container
Docker host:     8 CPUs, 7.7 GiB memory

Redis and its memory limit

Ferry tells Redis to use 3/4 of its memory limit for data.

Limits in a blueprint

In a blueprint, a plan or the keys memoryLimit and cpuLimit set the limits.

On this page

Change the defaultsSee the defaults