A GitHub Action to set up Cloudflare WARP on GitHub Actions runners. Routes all runner traffic (including Docker containers) through Cloudflare's network with automatic retries and connectivity verification.

• Two modes — WARP client (recommended) or WireGuard
• Docker support — automatically configures Docker containers to route through WARP
• Automatic retries — configurable retry attempts with exponential backoff
• Connectivity verification — verifies WARP tunnel is active before proceeding
• DNS configuration — sets Docker daemon DNS to Cloudflare (1.1.1.1) and Google (8.8.8.8)
• Dual-stack — supports IPv4-only, IPv6-only, or dual-stack

steps:
  - uses: viperadnan-git/setup-warp@v1

steps:
  - name: Set up WARP
    uses: viperadnan-git/setup-warp@v1
    with:
      mode: client        # or 'wireguard'
      stack: dual         # or 'ipv4', 'ipv6'
      retries: 3
      configure_docker: true

  - name: Run something through WARP
    run: curl https://cloudflare.com/cdn-cgi/trace

When configure_docker is enabled (default), Docker containers automatically route through WARP:

steps:
  - uses: viperadnan-git/setup-warp@v1

  - run: |
      docker run --rm alpine sh -c "wget -qO- https://cloudflare.com/cdn-cgi/trace"
      # Output will show warp=on

This works by:

1. Configuring Docker daemon DNS to use Cloudflare/Google DNS
2. Installing a transparent wrapper that injects --network host into docker run commands

Uses the official Cloudflare WARP client. Registers fresh credentials on each run, making it more reliable than shared WireGuard keys.

- uses: viperadnan-git/setup-warp@v1
  with:
    mode: client

Uses a WireGuard tunnel with pre-configured Cloudflare WARP credentials. Lighter weight but uses shared keys.

- uses: viperadnan-git/setup-warp@v1
  with:
    mode: wireguard

1. Installs WARP — downloads and installs the Cloudflare WARP client or WireGuard tools
2. Connects — establishes the WARP tunnel (client mode registers fresh credentials each run)
3. Verifies — confirms connectivity and that warp=on via Cloudflare's trace endpoint
4. Configures Docker — updates Docker daemon DNS and installs a wrapper for container networking
5. Retries — if any step fails, tears down and retries with exponential backoff
6. Debug dump — on final failure, prints network interfaces, routes, DNS config, and WARP status

• Runners: Ubuntu (20.04, 22.04, 24.04)
• Architecture: amd64 (auto-detected via dpkg --print-architecture)

Inspired by fscarmen/warp-on-actions. Rewritten with Docker networking fixes, robust error handling, retry logic, and connectivity verification.

MIT