FerryDocs

Start ferryd

Three commands load the unit, start ferryd now and at each boot, and show its log.

Edit on GitHub
Unit fileferryd.servicesystemdferrydJournaljournalctl

daemon-reload: systemd reads the new unit file.

1 / 3

Load the unit

systemd reads the new file.

Terminal
sudo systemctl daemon-reload

Start ferryd

Terminal
sudo systemctl enable --now ferryd

starts ferryd now, and at each boot.

Read the log

Terminal
sudo journalctl -u ferryd -n 30

The command shows the last 30 lines that ferryd wrote to the .

Output (excerpt)
  Ferry 0.1.0 is running
  Dashboard + API : http://127.0.0.1:7878
  Dashboard (proxy): disabled (enable with --dashboard-host ferry.apps.example.com)
  Apps            : https://<name>.apps.example.com
  Docker          : 27.3.1 (4 CPUs, 7.8 GiB)
  Data            : /var/lib/ferry
  Limits          : 512 MiB / 1 CPU per container (default), 1024 pids, logs rotated at 10 MiB × 3
  Free disk check : deploys need 1 GiB free

  Create your account: http://127.0.0.1:7878/setup?code=5b0e…

What the output tells you

LineMeaning
Create your accountThe link that creates the account of the server. You open it on the next page.
DockerThe CPUs and the memory of the .
LimitsThe container limits that Ferry applies.
Free disk checkThe free-disk check that Ferry applies.

If a default limit is more than the host has, ferryd writes a warning at startup. It does the same if the kernel of the host cannot enforce CPU limits.

On this page