Dan Nicholson

I moved away from this because we were going to EOL the product that this affects, but now that decision has been reversed. My plan here is: * Refactor `ostree_admin_option_context_parse`...

> You're right that there are a ton of options that will cause a mount namespace to be created, but we can just basically not use any unit options in...

> A cool thing IMO about https://github.com/coreos/coreos-assembler is that the entire build and test tooling is one (large) container image you can run anywhere you like. Though it also requires...

I think this is ready to review again. I ended up not touching the `ostree_admin_option_context_parse` and instead just calling it twice with different flags depending on the context. That seems...

@jallwine for the uEnv.txt, I was sure we had managed the environment variables at Endless, but when I looked closer there wasn't any of that. Apparently we've always just embedded...

When you create the initramfs, you need to put the stuff from ostree in it. What the ostree initramfs integration does is run `ostree-prepare-root` just before the `pivot_root`. This is...

It's pretty system dependent, but ostree's initramfs integration is provided by dracut. The way you'd probably do this is `chroot` into the unpacked image and then run `dracut --add ostree...

I think you could probably use switchroot.sh like you were trying, but I think it's been unmaintained for a while. So it's likely missing some more recent changes like `/run/ostree-booted`....

Interesting. At first this made me think of an [OCI image index](https://github.com/opencontainers/image-spec/blob/main/image-index.md) or [Docker manifest list](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list) where one ref would point to multiple arches, but I don't think that's what...

This is fine by me. I'd rather fix it all in one mega commit than hundreds of little fixes scattered in PRs.