Create the custom hosts file, there is no minikube with IP added.

[charleech]

• minikube v1.20.0 on Centos 7.7.1908
  • MINIKUBE_HOME=/opt/minikube.home
• Using the docker driver based on user configuration
• Starting control plane node minikube in cluster minikube
• Pulling base image ...
• Creating docker container (CPUs=16, Memory=8000MB) ...
• Preparing Kubernetes v1.20.2 on Docker 20.10.6 ...
  • opt bip=172.18.0.1/16
  • Generating certificates and keys ...
  • Booting up control plane ...
  • Configuring RBAC rules ...
• Verifying Kubernetes components...
  • Using image gcr.io/k8s-minikube/storage-provisioner:v5
• Enabled addons: storage-provisioner, default-storageclass
• Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

Steps to reproduce the issue:

1. Create the $MINIKUBE_HOME/.minikube/files/etc/hosts with the following content: -

127.0.0.1       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

172.17.x.x my.some.host1
172.17.x.y my.some.host2

2. Start the minikube.
3. Access the shell via minikube ssh.
4. Inside the shell execute the cat /etc/hosts.

::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

172.17.x.x my.some.host1
172.17.x.y my.some.host2
#
#<--- There is no `192.168.49.2 minikube` here.
#
192.168.49.1    host.minikube.internal
192.168.49.2    control-plane.minikube.internal

Full output of minikube logs command:
N/A

Full output of failed command:
N/A

[afbjorklund]

Related issue to #11220

Works here, though:

192.168.49.2	minikube
192.168.49.1	host.minikube.internal
192.168.49.2	control-plane.minikube.internal

When not providing your own file, without it...

Looks like the hostname is set before files are copied.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten