Benjamin Gilbert
Benjamin Gilbert
Awesome, thanks for the detailed proposal! > I'd personally put this into the `security` map next to TLS because this touches base line security for the machine The `ignition` section...
Yup, that's right.
Looking at the output of `podman generate systemd`, I'm not seeing anything sufficiently complex to be worth delegating to another tool. Any reason we shouldn't just generate the unit ourselves?
Is this for the `core` user or the other one? Is there a previous version of Container Linux where this was working properly?
If you're just starting with Container Linux, please use a [Container Linux Config](https://coreos.com/os/docs/latest/provisioning.html) rather than a cloud-config. coreos-cloudinit is long deprecated and has unfixable race conditions. It seems likely that...
At this point you should start with a new VM. Ignition only runs on the first boot, and anyway coreos-cloudinit has already made a bunch of changes to your system.
`veth*` is not managed by networkd, but networkd still creates a status file in `/run/systemd/netif/links/`.
@tpgxyz Thanks for reporting upstream! https://github.com/systemd/systemd/pull/8611 should fix the issue for systemd 239.
Container Linux is now in deep maintenance mode and we're not likely to apply this update.
This was an intentional change in https://github.com/coreos/scripts/pull/817. Is it causing a problem for you?