field networkd not found in type v1_0.Config

[philiprhoades]

People,

I get:

# ./fcct/bin/amd64/fcct -pretty -strict -input config_network.fcc 
Error translating config: yaml: unmarshal errors:
  line 9: field networkd not found in type v1_0.Config

What am I missing?

Thanks,
Phil.

[philiprhoades]

I think I know what is going on - networkd is not installed - I found:

coreos/fedora-coreos-tracker#24

Now looking at nmcli . .

[bgilbert]

There is no networkd block in FCCs. You can use the files block to write a NetworkManager key file.

[philiprhoades]

Benjamin,

On 2019-12-01 13:56, Benjamin Gilbert wrote: There is no networkd block in FCCs. You can use the files block to write a NetworkManager key file [1].

I can't see a "files" block on that page . . I can see an ipv4 "auto" option . . I eventually changed the IP manually on the installed and booted bare-metal machine using nmcli - which was some useful learning . . Thanks, Phil.

…

-- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [2], or unsubscribe [3]. Links: ------ [1] https://developer.gnome.org/NetworkManager/stable/nm-settings-keyfile.html [2] #55 [3] https://github.com/notifications/unsubscribe-auth/AAIZVJ3ZBKCLVLUJFPMOIFDQWMRWTANCNFSM4JTGIV3A

-- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: [email protected]

[bgilbert]

The files block is in the FCC itself.

We generally recommend performing all system configuration via the FCC, so that it includes the complete set of customizations to your system. That way, you can deploy additional copies of your system by just reusing the same provisioning config.