Supported Platforms for Docker-based Deployments
Firezone currently supports the following platforms for Docker-based deployments.
| OS | Architecture(s) | Runtime | Status | Notes |
|---|---|---|---|---|
| Linux | amd64 arm64 | Docker Server | Fully-supported | Kernel 5.6 or higher recommended. |
| Linux | amd64 arm64 | Docker Desktop | Works, but unsupported. | Not recommended for production deployments. See caveats. |
| macOS | amd64 arm64 | Docker Desktop | Works. but unsupported. | Not recommended for production deployments. See caveats. |
| Windows | amd64 arm64 | Docker Desktop | Untested | Not recommended for production deployments. See caveats. |
Docker Desktop caveats
Docker Desktop rewrites the source address for packets flowing out of container networks under some conditions. This can cause routing loops and other hard to debug connectivity issues with Firezone. We recommend only using Docker Server for Linux for production deployments.
Non-Linux platform caveats
Only Docker for Linux supports the host networking mode, so macOS and Windows
platforms will be able unable to properly attribute client source address for
HTTP requests. This means any IP-based throttling or logging in your chosen
proxy (caddy by default) will be ineffective, since the source IP will always
be the Docker-side host IP (typically 172.X.0.1).
Egress rules operate on the tunneled client IP address and aren't affected by this limitation.