kubernetes
/
minikube
mirror of https://github.com/kubernetes/minikube.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add useful tools in the Kicbase Docker image 

Signed-off-by: Peixuan Ding <dingpeixuan911@gmail.com>
pull/11384/head
Peixuan Ding 2021-05-11 21:49:37 -04:00
parent c214b040e6
commit 075ca20498
2 changed files with 17 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
deploy/kicbase/Dockerfile
View File

@ -63,6 +63,7 @@ RUN echo "Ensuring scripts are executable ..." \
libseccomp2 pigz \
bash ca-certificates curl rsync \
nfs-common \
iputils-ping netcat-openbsd vim-tiny \
&& find /lib/systemd/system/sysinit.target.wants/ -name "systemd-tmpfiles-setup.service" -delete \
&& rm -f /lib/systemd/system/multi-user.target.wants/* \
&& rm -f /etc/systemd/system/*.wants/* \

20
site/content/en/docs/handbook/host-access.md
View File

@ -11,7 +11,7 @@ aliases:
The service running on your host must either be bound to all IP's (0.0.0.0) and interfaces, or to the IP and interface your VM is bridged against. If the service is bound only to localhost (127.0.0.1), this will not work.
### host.minikube.internal
### `host.minikube.internal`
To make it easier to access your host, minikube v1.10 adds a hostname entry `host.minikube.internal` to `/etc/hosts`. The IP which `host.minikube.internal` resolves to is different across drivers, and may be different across clusters.
@ -32,8 +32,20 @@ PING host.minikube.internal (192.168.64.1): 56 data bytes
64 bytes from 192.168.64.1: seq=0 ttl=64 time=0.225 ms
```
To test connectivity to a specific TCP service listening on your host, use `telnet host.minikube.internal <port>`. Here are how to interpret the different messages:
To test connectivity to a specific TCP service listening on your host, use `nc -vz host.minikube.internal <port>`:
* `<nothing>`: You are connected! Hit Ctrl-D to get back to a shell prompt.
```sh
$ nc -vz host.minikube.internal 8000
Connection to host.minikube.internal 8000 port [tcp/*] succeeded!
```
Here are how to interpret the different messages:
* `Connection succeeded`: You are connected!
* `Connection refused`: the service is not listening on the port, at least not across all interfaces
* `Connection closed by foreign host`: the service is listening, but decided that your telnet client did not meet the protocol handshake requirements. Using a real client will likely work.
{{% alert title="Note" color="primary" %}}
When using an older version of minikube, you may have to manually install tools like `ping` and `netcat` within the minikube image:
```sh
sudo apt install iputils-ping netcat-openbsd
```
{{% /alert %}}