Add host.crc.testing to /etc/hosts

[bobbygryzynger]

Related to #4398: because the host can be reached at host.crc.testing this should be added to CRC's /etc/hosts modifications.

127.0.0.1    host.crc.testing

[cfergeau]

It is similar to this docker feature https://docs.docker.com/desktop/networking/#i-want-to-connect-from-a-container-to-a-service-on-the-host, I'm not sure this also can be resolved on the host?
However, this should be relatively easy to do in our case, so why not.

[praveenkumar]

host.crc.testing this should be added to CRC's /etc/hosts modifications.

@bobbygryzynger if host.crc.testing already available to consume in the CRC VM then why we need to modify /etc/hosts to have this entry?

[bobbygryzynger]

@praveenkumar I have some scripts that run both on the host and within containers on the cluster that interact with host services. It would be convenient to be able to use the same hostname in both circumstances and not have to set the value in the host's /etc/hosts myself. This would also help other developers setting up my project locally, by removing a manual step.

[cfergeau]

It is similar to this docker feature https://docs.docker.com/desktop/networking/#i-want-to-connect-from-a-container-to-a-service-on-the-host, I'm not sure this also can be resolved on the host?
However, this should be relatively easy to do in our case, so why not.

[praveenkumar]

host.crc.testing this should be added to CRC's /etc/hosts modifications.

@bobbygryzynger if host.crc.testing already available to consume in the CRC VM then why we need to modify /etc/hosts to have this entry?

[bobbygryzynger]

@praveenkumar I have some scripts that run both on the host and within containers on the cluster that interact with host services. It would be convenient to be able to use the same hostname in both circumstances and not have to set the value in the host's /etc/hosts myself. This would also help other developers setting up my project locally, by removing a manual step.