Mobile Proxy Docker Setup

Docker Proxy Environment

Docker proxy configuration is widely misunderstood because Docker operates across three isolated networking boundaries: the Docker daemon (dockerd), the build process (docker build), and running container instances (docker run). Setting a proxy in one layer does not propagate to the others. Understanding these three distinct scopes is essential to building reliable containerized proxy pipelines.

Container Proxy Configuration

To route outbound traffic from a container through a dedicated mobile proxy, supply the standard proxy environment variables at runtime. Most containerized runtimes (Python, Go, Node.js, cURL) automatically read these variables upon initialization.

docker run --rm \
  -e HTTP_PROXY="http://user123:secret456@proxy.pxm2.io:8000" \
  -e HTTPS_PROXY="http://user123:secret456@proxy.pxm2.io:8000" \
  -e NO_PROXY="localhost,127.0.0.1,host.docker.internal" \
  curlimages/curl:latest https://ipinfo.io/json

Alternatively, you can configure your Docker CLI client config file (~/.docker/config.json) to automatically inject proxy settings into all newly spawned containers without repeating -e flags.

{
  "proxies": {
    "default": {
      "httpProxy": "http://user123:secret456@proxy.pxm2.io:8000",
      "httpsProxy": "http://user123:secret456@proxy.pxm2.io:8000",
      "noProxy": "localhost,127.0.0.1,.internal"
    }
  }
}

Docker Compose Proxy Setup

In multi-container stacks, Docker Compose allows granular control over which services use mobile proxies and which communicate directly over local networks. For instance, scraping worker instances can route through dedicated 4G/5G modems while database and Redis cache services remain completely local.

version: '3.8'

services:
  scraper-worker:
    image: my-scraper:latest
    environment:
      - HTTP_PROXY=http://user123:secret456@proxy.pxm2.io:8000
      - HTTPS_PROXY=http://user123:secret456@proxy.pxm2.io:8000
      - NO_PROXY=localhost,127.0.0.1,postgres,redis
    depends_on:
      - postgres
      - redis

  postgres:
    image: postgres:16-alpine
    environment:
      POSTGRES_DB: scraper_data
      POSTGRES_PASSWORD: secretpassword

  redis:
    image: redis:7-alpine

Network-Level Proxy

Some containerized tools refuse to respect environment variables or lack proxy support in their code. In such scenarios, network-level routing or sidecar proxy patterns ensure all container traffic is redirected without modifying application source code.

By launching a sidecar container running redsocks or a WireGuard gateway connected to the mobile proxy host, you can route all outbound TCP streams from other containers sharing that network namespace.

# Service sharing the sidecar proxy network
services:
  proxy-gateway:
    image: custom-redsocks-gateway
    cap_add:
      - NET_ADMIN
    environment:
      - PROXY_SERVER=proxy.pxm2.io
      - PROXY_PORT=1080

  legacy-app:
    image: my-app:latest
    network_mode: "service:proxy-gateway"

Docker Proxy Troubleshooting

Common obstacles when configuring mobile proxies inside Docker containers and how to solve them:

Frequently Asked Questions

Related Mobile Proxy Guides

Explore setup tutorials for developer environments, automation scripts, and server configurations.

Developer & Automation Guides

Platform & Operating Systems