Follow the Using Multi-Node Clusters is not able to access the worker node. #11669
Comments
|
Full output of
|---------|--------------------------------|----------|-------|---------|-------------------------------|-------------------------------|
stderr: -- /stdout -- ** /stderr ** I0616 13:33:37.004230 3489548 cli_runner.go:115] Run: docker container inspect -f "'{{(index (index .NetworkSettings.Ports "22/tcp") 0).HostPort}}'" minikube I0616 13:33:37.177897 3489548 main.go:128] libmachine: SSH cmd err, output: : I0616 13:33:37.780244 3489548 ubuntu.go:71] root file system type: overlay [Service] This file is a systemd drop-in unit that inherits from the base dockerd configuration.The base configuration already specifies an 'ExecStart=...' command. The first directivehere is to clear out that command inherited from the base configuration. Without this,the command from the base configuration and the command specified here are treated asa sequence of commands, which is not the desired behavior, nor is it valid -- systemdwill catch this invalid input and refuse to start the service with an error like:Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services.NOTE: default-ulimit=nofile is set to an arbitrary number for consistency with othercontainer runtimes. If left unlimited, it may result in OOM issues with MySQL.ExecStart= Having non-zero Limit*s causes performance problems due to accounting overheadin the kernel. We recommend using cgroups to do container-local accounting.LimitNOFILE=infinity Uncomment TasksMax if your systemd version supports it.Only systemd 226 and above support this version.TasksMax=infinity set delegate yes so that systemd does not reset the cgroups of docker containersDelegate=yes kill only the docker process, not all processes in the cgroupKillMode=process [Install] [Service] This file is a systemd drop-in unit that inherits from the base dockerd configuration.The base configuration already specifies an 'ExecStart=...' command. The first directivehere is to clear out that command inherited from the base configuration. Without this,the command from the base configuration and the command specified here are treated asa sequence of commands, which is not the desired behavior, nor is it valid -- systemdwill catch this invalid input and refuse to start the service with an error like:Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services.NOTE: default-ulimit=nofile is set to an arbitrary number for consistency with othercontainer runtimes. If left unlimited, it may result in OOM issues with MySQL.ExecStart= Having non-zero Limit*s causes performance problems due to accounting overheadin the kernel. We recommend using cgroups to do container-local accounting.LimitNOFILE=infinity Uncomment TasksMax if your systemd version supports it.Only systemd 226 and above support this version.TasksMax=infinity set delegate yes so that systemd does not reset the cgroups of docker containersDelegate=yes kill only the docker process, not all processes in the cgroupKillMode=process [Install] I0616 13:33:37.967178 3489548 cli_runner.go:115] Run: docker container inspect -f "'{{(index (index .NetworkSettings.Ports "22/tcp") 0).HostPort}}'" minikube [Service]
|
spowelljr
added
co/multinode
|
After digging during the weekend, I've found that it is about the I've changed the minikube start --nodes 2 \
--docker-opt bip=172.18.0.1/16 \
--extra-config=kubeadm.pod-network-cidr=12.244.0.0/16 |
|
I'm not sure if there is any document mentioning about the |
|
Could you please help to point me to the proper direction? |
minikube versionminikube start --nodes 2 --docker-opt bip=172.18.0.1/16I follow the example from https://minikube.sigs.k8s.io/docs/tutorials/multi_node/ by creating the
hello-svc.yamlandhello-deployment.yamlas the following: -Steps to reproduce the issue:
minikube delete --all --purgeminikube start --nodes 2 --docker-opt bip=172.18.0.1/16kubectl get nodesminikube statuskubectl apply -f hello-deployment.yamlkubectl rollout status deployment/hellokubectl apply -f hello-svc.yamlkubectl get pods -o wideminikube service listFull output of
minikube logscommand:N/A
Full output of failed command:
N/A
The text was updated successfully, but these errors were encountered: