FerryDocs
GuidesProduction setup

Container logs

Ferry rotates the log of each container, thus a log cannot fill the disk.

Edit on GitHub
Containerstdout, stderrDocker log3 files × 10 MiBferry logs
About 30 MiB of log at most for each container

Docker stores what each container writes to and . With json-file, the default of Docker, Ferry sets the .

Flag and variableDefaultMeaning
--log-max-size FERRY_LOG_MAX_SIZE10MFerry rotates the log of each container at this size.
--log-max-files FERRY_LOG_MAX_FILES3The number of files that Ferry keeps, the current file included.

ferry logs NAME reads this output from Docker. Thus it goes back only as far as those files.

Docker fixes the log settings when it creates a container. Thus a change applies only to the containers that Ferry creates after it.

Where the other logs go

LogPlace
The server log of ferrydIts standard output. systemd sends it to the (journalctl -u ferryd), which has its own size limits.
Deploy logs and job logsFiles in the data directory.
<data-dir>/ferryd.logOnly a server that you start in the background with ferryd start writes this file.

The free-disk check

Before a build, Ferry makes sure that the disk has 1 GiB free, or the deploy fails early.

Behind another reverse proxy

If another program owns ports 80 and 443, run the Ferry proxy on a local port behind it.

On this page

Where the other logs go