Open vboufleur opened 4 years ago
I'm serving the files over the Web with Nginx, default settings.
Hmm, does the output show whether NetworkManager tries to bring up networking? What version of the FCOS live ISO are you using? Might be a regression from https://github.com/coreos/fedora-coreos-config/pull/326. One sanity-check is (if you have access to the kernel cmdline) to add rd.neednet=1
and see if it works.
Adding rd.neednet=1
to the kernel command line solved it for me. Thanks!
A doc page detailing all possible kernel command line options for Fedora CoreOS would be great. It would help other people that stumble on this issue.
Re-opening. We need to double check that one doesn't have to add rd.neednet=1
if an Ignition config is embedded.
hey @vboufleur - what version of the LiveISO are you using? A filename should suffice.
@dustymabe this is the ISO version: fedora-coreos-31.20200407.3.0-live.x86_64.iso
I'm having a similar problem. I have embedded an ignition into an image that looks like this:
variant: fcos
version: 1.0.0
ignition:
config:
replace:
source: http://169.254.169.254/hetzner/v1/user-data
In my case rd.neednet=1
is present in the kernel cmdline. I'm not sure if it is possible to use an ipv4ll address here, but using this pattern would make it possible to use hetzners user_data
endpoint without modifying the ignition code. The errors are similar to those of @vboufleur
Ok, i debugged my problem. It was just a typo in the source url (should end with userdata
instead of user-data
). Sorry for that.
Re-opening. We need to double check that one doesn't have to add
rd.neednet=1
if an Ignition config is embedded.
OK I looked at this a bit today (sorry for the delay). From what I understand the problem isn't actually the install boot that needs the network, but rather the subsequent first boot (ignition boot) of the installed system. I think the tricky part here is that passing any --firstboot-args
to coreos-installer will overwrite the default networking kargs (defaulting to ip=dhcp,dhcp6 rd.neednet=1
). We need to decide if this is a bug or not, though I will note the problem will probably go away once we implement https://github.com/coreos/fedora-coreos-tracker/issues/460 .
@vboufleur a workaround for now is to add ip=dhcp,dhcp6 rd.neednet=1
to your firstboot kargs so they'll get added. Be careful doing that in the script in the fcct from my blog post, though, as the quoting gets tricky in bash. I probably should have used more than one arg in that example.
Hi all!
I'm working on a bash script that will takeover cloud Ubuntu 16.04 instances and install CoreOS on top of them. I'm Live ISO booting CoreOS on a VPS (OVH) with a (1) base ignition config embedded with a bash script that will call
coreos-installer
and pass to it another (2) ignition config that will source a (3) external ignition config.But this second config file is failing to fetch the third, networked, external one. First it was set to source the file with a direct IP:
The link works: http://54.39.179.16/ignition.network.json
But this failed:
Then I tried with DNS:
It fails too:
Here's the source file.
Based Live ISO embedded config (1) and (2):
Any help would be dearly appreciated.
Shoutout to @dustymabe who made this wonderful article that inspired me to make the script above: https://dustymabe.com/2020/04/04/automating-a-custom-install-of-fedora-coreos/