Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
multiple OEM-GCE container get started on GCE when using non-Google DNS #2601
Instead of a single continuous running oem-gce rkt container we found that every 1-2 minutes a new oem-gce container instance was spinning up until the system runs too many of them and in the end runs out of memory.
Container Linux Version
We run CoreOS on Google Cloud VMs since some years. Cloud is connected via site-2-site VPN to our corporate network.
Only one oem-gce container should be started after boot and stay running
every 1-2 minutes a new oem-gce rkt container instance is spinning up and stays running until we get OOM issues
deploy a VM with latest CoreOS image on google cloud
from journal we got these logs that seem to relate to the issue
As a workaround we found out that once I add nameserver 169.254.169.254 as first entry to resolver.conf before our corporate nameserver the problem disappears.
Looks like something has changed inside oem-gce container so that just adding the metadata.google.internal entry inside hosts file is not sufficient any more to allow the container to start properly even this config worked fine for years.
In older versions 1576 and 1855 the problem did not exist. It even looks like that the latest CoreOS version does not show this problem as long a the oem-gce-container version is old. This we found on one machine that was deployed long time ago and got updated continuously. During these updates obviously the oem-gce- container was not updated.