Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
coreos-metadata.service: Caused by: Couldn't find 'coreos.oem.id' flag in cmdline file (/proc/cmdline) #2303
Container Linux Version
core@coreA11 ~ $ cat /etc/os-release
Hardware: Bare-metal Ubuntu running Libvirt/Kvm with CoreOS as the guest VM
coreos-metadata.service agent should start
jforman@desktop1:~$ ssh email@example.com
core@coreA11 ~ $ systemctl status coreos-metadata.service
Dec 25 14:08:28 coreA11 systemd: Starting CoreOS Metadata Agent...
core@coreA11 ~ $ cat /usr/lib/systemd/system/coreos-metadata.service
Reboot the VM. Any login. The service just doesn't start.
I used the vagrant-virtualbox config transpiler platform for creating my ignition config.
I plan to try to hack on the coreos-metadata repo to add support for libvirt as a provider (vagrant-virtualbox does not work as a provider since it expects eth1 as the network interface, where as libvirt provides eth0 by default).
I don't expect coreos-metadata to support any platforms without a metadata service. The intention of coreos-metadata is just to consolidate all of the
You can use something like this example as your service. It fundamentally the same way as coreos-metadata, it just doesn't have any fancy code. I hope that makes sense.
Apologies up front if these questions are "stupid", I'm just getting up to speed and had a few questions:
1) Do I need to manually add a