FerryDocs

The three logs

Ferry has a deploy log, a runtime log and a job log. Each one has its own place.

Edit on GitHub
Deploy logone for a deployJob logone for a runRuntime logof the containersData directoryfiles of FerryDockerwith the container
Where each log is
LogWhat it hasRead it
The build output and the deploy steps of one deployferry logs --deploy ID
What the containers of the service write to and ferry logs NAME
The output of one job runferry logs --job ID

Where a log is, and how long

LogPlaceKept
Deploy log<data-dir>/logs/deploys/<deploy id>.logUntil you delete the service
Runtime logIn DockerAs long as the containers exist. Docker rotates it at 10 MiB × 3 files for each container (the default).
Job log<data-dir>/logs/jobs/<job id>.logFor the newest 100 runs of each service

The parts of a line

Deploy log
09:38:31 ==> Starting 1 instance(s)
09:38:31 [2fa90d] docker-echo listening on :8000

Each line has a and a stream: stdout, stderr or system. A line of a runtime log also has its instance.

The messages of Ferry are system lines. They start with ==> .

On this page