<p>Edit - this is on OSX
Also, I've tried running <code>minikube service &lt;service-name&gt;</code>, that's shown below and when it tries to open it in a browser I get a "connection refused" signal because the port is closed.</p>

<p>I have a kubernetes deployment that works fine when using <code>--driver=virtualbox</code>. I translated this to use <code>--driver=docker</code> and this almost works except when I do the following</p>

<pre><code>$ minikube service websocket-nodeport
|-----------|--------------------|-------------|-------------------------|
| NAMESPACE |        NAME        | TARGET PORT |           URL           |
|-----------|--------------------|-------------|-------------------------|
| default   | websocket-nodeport |        9000 | http://172.17.0.4:30007 |
|-----------|--------------------|-------------|-------------------------|
🏃  Starting tunnel for service websocket-nodeport.
|-----------|--------------------|-------------|------------------------|
| NAMESPACE |        NAME        | TARGET PORT |          URL           |
|-----------|--------------------|-------------|------------------------|
| default   | websocket-nodeport |             | http://127.0.0.1:62032 |
|-----------|--------------------|-------------|------------------------|
🎉  Opening service default/websocket-nodeport in default browser...
❗  Because you are using a Docker driver on darwin, the terminal needs to be open to run it.
</code></pre>

<p>But if I go to </p>

<pre><code>$ curl http://127.0.0.1:62032
curl: (7) Failed to connect to 127.0.0.1 port 62032: Connection refused
</code></pre>

<p>nothing happens, it isn't a valid address. However, if I do the following</p>

<pre class="lang-sh prettyprint-override"><code>$ minikube ssh
# inside the VM now
docker@minikube:~$ curl http://172.17.0.4:30007
ok!: websocket-frontend-b7c8dc4b9-5jtg6
</code></pre>

<p>I get the response I want! So this means that my service is running and the URL output of the <code>websocket-nodeport</code> address as is internal to minikube is correct but for some reason the local address <code>http://127.0.0.1:62032</code> isn't be forwarded to the minikube VM.</p>

<p>How do I get this forward to work?</p>

John Allard
<p><code>$ minikube service &lt;service-name&gt;</code>
this will open up a tunnel to connect to the service, make sure the service is a NodePort service.</p>
<p>If it opens a browser and you get a <code>404</code> this is because the url in the address bar doesn't exist within your api. Changing the URL PATH to correct URL paths/routes you defined in your API should fix this</p>
