You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
In an air-gapped cluster with IP and DNS servers set by DHCP, if you enable the open-vm-tools service, then upon boot ROS will attempt to start the service and pull the image before the DNS servers have necessarily been updated by DHCP. As a result the default Google public DNS resolvers are used, which being unreachable, results in the service failing to start.
RancherOS Version: (ros os version)
v1.5.4
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
VMWare
The text was updated successfully, but these errors were encountered:
I think that in VMware environments you are supposed to use the rancheros-vmware release artifacts since they have the open-vm-tools already bundled and won't require downloading them.
Starting open-vm-tools after DHCP will actually lead to a couple of new problems, for example:
Longer boot times in environments without DHCP (as it will wait to acquire DHCP lease)
cloud-config network configuration provided by Guest-Info mechanism will not be applied to DHCP client
In an air-gapped cluster with IP and DNS servers set by DHCP, if you enable the open-vm-tools service, then upon boot ROS will attempt to start the service and pull the image before the DNS servers have necessarily been updated by DHCP. As a result the default Google public DNS resolvers are used, which being unreachable, results in the service failing to start.
RancherOS Version: (ros os version)
v1.5.4
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
VMWare
The text was updated successfully, but these errors were encountered: