Why Does the Astra CLI Require Docker?
Last updated: June 11, 2026
Introduction
Astra's CLI runs inside a Docker container to ensure it works consistently across different environments without requiring manual dependency setup on your machine.
What Runs Inside the Container
The CLI bundles two tools internally:
mitmproxy — intercepts HTTP/S traffic for capture
OpenTelemetry Collector — collects and forwards traces and metadata
Both tools have specific system-level dependencies and network requirements. Packaging them in Docker means you get a working setup without installing or configuring anything beyond Docker itself.
Why Docker Specifically
Consistency — the CLI behaves the same way regardless of your OS or local software stack, with no conflicts with existing tools or Python environments.
Simplified setup — no manual dependency management. Install Docker, run the CLI.
Reliable networking — traffic capture via proxy requires specific port and routing configurations that Docker handles predictably across platforms.
What the CLI Supports
Once running, the CLI enables two primary workflows:
Setting up a proxy to capture live API traffic
Importing traffic from tools like Burp Suite
Can't Use Docker?
Reach out to help@getastra.com or raise a support ticket. The team can help you explore alternative approaches for submitting API traffic securely.