Container Linux config fails the Ignition validation test

[naisanza]

The Container Linux config fails the Ignition validation test

# This config is meant to be consumed by the config transpiler, which will
# generate the corresponding Ignition config. Do not pass this config directly
# to instances of Container Linux.

passwd:
  users:
    - name: core
      ssh_authorized_keys:
        - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDGdByTgSVHq.......

https://coreos.com/os/docs/latest/installing-to-disk.html#container-linux-configs

[lucab]

I'm confused. As you mentioned, you are trying to validate a ContainerLinux config against an Ignition (and cloudinit) validator, and it correctly tells you that it is invalid. Passing that to Ignition (or cloudinit) will indeed result in a failure. What is the actual issue?

[naisanza]

@lucab This was the result from 20-minutes of ever touching CoreOS (I mean Container Linux) for the first time.

Skimming through docs just to find what I need to:

1. Install to disk
2. Login

When it installed but I couldn't login, I went straight to Google. Since there's no default password, I went back to looking at the install process. It talked a lot about YAML and JSON, which I just wasn't interested.

My initial cloud-config.yml looked like this, I found it on some site and just wanted it to work, and with a lot less lines than what the other examples looked like, so I just went with it:

#cloud-config
ssh_authorized_keys:
  - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDGdByTgSVHq

Also, when I copied and pasted it into the Ignition validator (before I really knew how any of it related to each other), it passed, so I figured I was on the right track:

Hence, why I thought the YAML config should work with the Validator, because my original YAML passed.

After 6 different combinations of failures to get it installed and the login working, I gave in and skimmed less aggressively

[lucab]

Thanks. I know the situation with ct/ignition/cloud-init is unfortunately confusing, but quick-skimming docs probably didn't help. We'll see if we can improve the situation in some way.

@dgonyeo not sure about current validator backend, but perhaps we can return better results on positive validation, like "Input correctly validated as Ignition configuration, schema vX (+hint to upgrade if non-latest)." and "Configuration correctly validated as cloudinit configuration. This type of configuration is deprecated, please consider using cl-config/ct instead."?

[cgonyeo]

Yeah that'd definitely be good. I'll look into it.