Unable to start on a mac due to multiple interfaces.

[kusold]

❯ docker-compose logs --follow                             
Attaching to docker_tor-router_1                           
tor-router_1     | Verifying environment                   
tor-router_1     | Container should only have the `eth0` and `lo` interfaces                                          
tor-router_1     | Additional interfaces should only be added once tor has been started                               
tor-router_1     | Killing to avoid accidental clobbering  
docker_tor-router_1 exited with code 1

/opt/tor-router # ip link show | awk '/^[0-9]*:/ {print $2}' | sed -e 's/:$//' -e 's/@.*$//'                           
lo                           
tunl0                        
gre0                         
gretap0                      
ip_vti0                      
ip6_vti0                     
sit0                         
ip6tnl0                      
ip6gre0                      
eth0

[flungo]

Are you running with --net=host? This is not supported.

What do you get if you run docker run --rm flungo/tor-router ip link?

[kusold]

Sorry for the severe delay on the response. I believe this has to do with how docker runs on macs.

❯ docker run --rm flungo/tor-router ip link                         
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1                                                              
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00           
2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1        
    link/ipip 0.0.0.0 brd 0.0.0.0                                   
3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN qlen 1         
    link/gre 0.0.0.0 brd 0.0.0.0                                    
4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN qlen 1000                                                         
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff              
5: ip_vti0@NONE: <NOARP> mtu 1332 qdisc noop state DOWN qlen 1      
    link/ipip 0.0.0.0 brd 0.0.0.0                                   
6: ip6_vti0@NONE: <NOARP> mtu 1500 qdisc noop state DOWN qlen 1     
    link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00                    
7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1         
    link/sit 0.0.0.0 brd 0.0.0.0                                    
8: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN qlen 1      
    link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00                    
9: ip6gre0@NONE: <NOARP> mtu 1448 qdisc noop state DOWN qlen 1      
    link/[823] 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00                      
34: eth0@if35: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP                                                 
    link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff 

[flungo]

No worries. Yes, that does seem like a different behaviour to what happens on Linux. If you are using this as a proxy, it would probably be best to find an image that just runs tor as a proxy (and doesn't need to configure iptables). As mentioned in #3, I may add environment variables to disable features which may make it usable as a proxy under MacOS but I'll have to do this when I have time.