Running rig without sudo

[potterme]

Currently "rig start" and "rig stop" prompt for a sudo password. Some clients are in a secure environment and are not allowed to elevate their account via sudo.

Mostly this only seems to affect the network setup for DNS. The rest of outrigger seems to work fine. Here are the steps we used to get around this.

1. For dnsdock to work, a route needs to be added to the system. This still requires an Admin account, but can be done separate from the "rig start".
   a) Determine the IP address of docker-machine: "docker-machine ip dev"
   b) "sudo route -n add 172.17.0.0/16 192.168.99.100" (replace 192.168.99.100 with the IP from a)

Now go to your regular user account

2. Typically in a secure environment, the client will have a different DNS Nameserver. Outrigger will use 8.8.8.8 as a fallback. If that is not accessible, do
   a) cat /etc/resolv.conf on local Mac to determine current DNS nameserver
   b) "export RIG_NAMESERVERS=1.2.3.4:53" (replace 1.2.3.4 with the nameserver IP from a)

Now you can do "rig start". When prompted for sudo password, just fail it until it continues. An option to skip this step will be added to rig in the future.

Run "rig doctor". If the above is successful then everything will look fine. If you still get an DNS error then something still isn't working. Also, you should be able to "ping dnsdock.outrigger.vm".

[febbraro]

To make it persistent across reboots we may need to point out something like this:

http://meinit.nl/add-permanent-static-route-mac-os-x