Benjamin Gilbert

Yeah, understood. Even in that case, though, the final config would now be specified in a mix of two languages/locations.

That wildcard is problematic for another reason: the semantics of the resulting config are dependent on the merge order. The usual solution is to add sequence numbers to filenames, but...

@tkarls Butane doesn't currently have any docs about config merging because Butane doesn't do the merging itself. See the [Ignition operator notes](https://coreos.github.io/ignition/operator-notes/#config-merging) for more info. @cgwalters: > In my case,...

@alvarlagerlof Right now, the inputs to config merging are Ignition configs, not Butane configs. You can use Butane to generate both configs, but the child config referenced by the parent...

On FCOS you can't create mountpoints directly in `/`; see docs [here](https://docs.fedoraproject.org/en-US/fedora-coreos/storage/#_configuration_in_etc_and_state_in_var). If you set `path` to `/var/mnt/external` it should work, and will automatically create the mountpoint.

Actually, yeah, that's a good idea.

https://github.com/coreos/fedora-coreos-config/pull/1879 aims to provide a way to create paths in the root directory. We might want to provide Butane sugar for that, but it doesn't completely obviate this issue, since...

@ramayer If this is still causing problems, we can reopen. What behavior are you seeing?

@saj We're triaging issues that are unlikely to be fixed in Container Linux, now that the focus of new development is shifting to Red Hat CoreOS and its community counterpart....

- Rather than `crashkernel: 128M`, maybe something like `reserved_mib: 128`? - Is it common to want to pass additional arguments to the dump kernel? Or can we let the user...