You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker version (e.g. docker -v): 1.12.1, build 6f9534c
What happened:
I've noticed that using minikube + xhyve and the default network driver (virtio-net), packets from container are not properly "NATed".
What you expected to happen:
minikube shoud add a pf rule in order to properly manage outgoing packets.
How to reproduce it (as minimally and precisely as possible):
start minikube
apply or create a deployment, go into the container and try to ping something on the outside world
tcpdump on the host (mac)
Anything else do we need to know:
In my case, I use a VPN for accessing some others resources, (the VPN create a utun0 iface), I used this pf rule in order to properly NAT outgoing minikube traffic.
echo "nat on {utun0} proto {tcp, udp, icmp} from 192.168.64.0/24 to any -> {utun0}" | sudo pfctl -a com.apple/utun0nat -f -
The text was updated successfully, but these errors were encountered:
BUG REPORT
Minikube version (use
minikube version
):v0.11.0
Environment:
Mac OS X Yosemite (10.10.5)
xhyve
docker -v
):1.12.1, build 6f9534c
What happened:
I've noticed that using
minikube
+xhyve
and the default network driver (virtio-net
), packets from container are not properly "NATed".What you expected to happen:
minikube
shoud add a pf rule in order to properly manage outgoing packets.How to reproduce it (as minimally and precisely as possible):
Anything else do we need to know:
In my case, I use a VPN for accessing some others resources, (the VPN create a
utun0
iface), I used this pf rule in order to properly NAT outgoing minikube traffic.The text was updated successfully, but these errors were encountered: