Benjamin Gilbert

> The full option syntax enables setting memory size dependent values and offset but I don't know if that's something we want to support. I suspect that's a pretty unusual...

> > Would it make sense to provide target-specific sugar? > > AFAIK, the kdump.conf docs say that "only one dump target and path can be specified". Ah, okay. Even...

It's not required, and we can always add it later. I'd note, though, that the linked example in OCP docs is not trivial. It has one service enablement, one karg,...

Are you still seeing this on current releases of Container Linux?

This seems plausible to me, though I may have missed something. The advantage of the current spec stabilization process is that it's well-documented, mostly mechanical, and doesn't require a lot...

Thanks for your report. This issue tracker is for Fedora CoreOS, and you appear to be talking about CoreOS Container Linux. (The terminology is confusing, we know.) I'll move this...

Are you still seeing this on current versions of Container Linux?

We've tried a couple times to update to a newer Docker release, but encountered crashes that we weren't able to address. The history is in https://github.com/coreos/coreos-overlay/pull/3477. There are no plans...

You can use Ignition's `storage.files` section to write SSH host keys and sshd configuration. For the latter, you can append to `/etc/ssh/sshd_config` (not recommended) or, with newer versions of sshd...

Yes, it'd be helpful if you can provide as complete an example as possible. Thank you! We'd normally put sugar for specific services into its own top-level struct, e.g. `ssh`.