Andrew Jeddeloh

As a first step, can you test with the latest beta, stable and alpha. They all have different kernels so if one of them works that would greatly narrow down...

I think it would be good to make this more general for launching containers in general, though that require adding something like `runtime-args` for things `--volume` and `--privileged`. Maybe something...

Can you post the contents of the mount unit (either a handwritten one or the one that gets generated)?

CL doesn't support having multiple USR-A / USR-B / EFI-SYSTEM / OEM partitions. I suspect that on update the kernel in one EFI-SYSTEM is getting updated and the USR A/B...

I'd be hesitant to use `-a` since that may trim filesystems that user does not want trimmed, but yeah, this shouldn't error. Perhaps the unit should have a `ConditionPathExists=/etc/fstab` instead?

`/etc/fstab` doesn't really have special meaning. Systemd doesn't even use it directly, a generator reads it and generates mount units which systemd then uses. The default filesystems for CL have...

I can't trivially reproduce this just running `systemctl start docker && lsof`. Do you have a minimal reproduction case? Also the version of Container Linux you're running is quite old....

As a workaround you can add a dropin unit to the `etcd-member.service` unit setting that environment variable. This is because we currently only support the command line options from etcd...

Is this new with that release or does it also affect older versions?

I agree this sounds like a kernel issue. Can you reproduce on the latest alpha or beta? They're running slightly newer kernels which will tell us if the fix is...