Docker Compose: Report imports never process because faraday-default-worker starts faraday-server

[brandonscholet]

Summary

Using the default docker-compose.yaml, report uploads complete successfully but are never imported into the selected workspace.

The server accepts the upload, parses it, and queues it for processing, but the queue is never consumed.

Environment

• Faraday: current master
• Docker Compose
• Ubuntu 24.04
• Fresh installation following the Docker installation guide

Steps to Reproduce

1. Deploy Faraday using the provided docker-compose.yaml.
2. Create a workspace.
3. Upload an Nmap XML report.
4. Observe that the upload never processes.

Expected Behavior

The uploaded report should be processed by the worker and imported into the workspace.

Actual Behavior

The upload succeeds and the server logs:

Faraday objects sent to celery in bulk for workspace <Workspace 1>

However, nothing is imported.

Redis shows the queue continuing to grow:

docker compose exec redis redis-cli llen celery
(integer) 8

Investigation

Inspecting the worker container showed:

docker top faraday_worker

Output:

bash /entrypoint.sh faraday-worker
/src/.venv/bin/python3 /src/.venv/bin/faraday-server --bind 0.0.0.0

The worker container appears to start another faraday-server instance rather than faraday-worker.

The image entrypoint ends with:

echo "$(date) Starting Faraday server ..."
faraday-server --bind 0.0.0.0

which appears to ignore the command supplied by Docker Compose.

Workaround

Changing the worker service from:

command: ["faraday-worker"]

to:

entrypoint: ["faraday-worker"]
command: []

results in:

docker top faraday_worker

showing:

/src/.venv/bin/python3 /src/.venv/bin/faraday-worker

Immediately after this change, queued imports began processing successfully.

I'm not certain whether the correct fix belongs in the Docker image entrypoint or the compose configuration, but this workaround consistently resolves the issue.