Docker force container to specific physical interface

I’ve been searching around the internet for the past week or so to find a solution to this, but so far I have come up empty handed.

There are three network interfaces available to my host, and I need to execute a phantomjs script on the wlan1 interface.

  • Can't access the dockerized app launched from the command line from outside
  • Share localhost with docker container
  • Can't use yum inside Docker container running on CentOS
  • Deploying a network of containers in a single K8s pod
  • AWS EC2 Docker Volumes lsblk
  • Docker set read timeout for push
  • My idea was to utilize Docker, but am running into issues locking a container to a specific interface.

    Here’s what I’ve tried, all either redirects to another interface, or has no network access. The only method that allows explicit access to the interface I need is by turning off all other interfaces.


    ExecStart=/usr/bin/docker daemon -b=wlan1 --ip= -H fd://


    version: "2"
        driver: bridge
          - open_network_1

    I’ve also fiddled with ip routing, and iptables

    ip route del
    ip route add dev wlan1 proto kernel scope link src
    iptables -t nat -A POSTROUTING -s -j SNAT --to-source

    172.19 would be the subnet created by the docker-compose network, would be the ip assigned to the wlan1 interface.

    Any insight would be appreciated, and I’m sure will help those with similar goals.

  • All node modules in package.json are being re-downloaded after small change
  • Update docker-contanier jre timezone
  • Increment command timeout in EBS from the -AWS
  • Openshift oc new-app command getsockopt: connection refused error
  • Access webcam using OpenCV (Python) in Docker?
  • What's main difference between Docker and Kubernetes
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.