Jon Polom

I gathered there was divergent functionality here and this was not really supported now. What is the present day workaround? ~~What is going on in your PR with `let target_etc...

> As for a workaround, should I just dump stuff into `/ostree/deploy/default/deploy//etc/`? What I've come up with to use in a script with a filesystem install to get to this...

> > ostree admin status --sysroot= doesn't work right after install as it reports No deployments. > > It's almost certainly because you have a distinct `/boot` filesystem which isn't...

~~I will try it and let you know what I find.~~ It appears to do some kind of logging. At a minimum a documentation improvement is needed to ensure that...

Does this more or less follow the same code path as the previous env var method? Output looks quite similar.

> But taking it one step up, we could easily also record the reference to the input, and add a `bootc factory-reset` command that would build on top of [reinstallation](https://github.com/containers/bootc/pull/137)...

I do not think bootc fits the mold of a tool requiring any form of IPC. It isn't a persistent process today and should never be in the future.

> We need to look into some workflow to handle properly verifying images before rebasing on a signed keyless image. What you're after appears to be completely broken/unsupported by the...

> > which in my opinion adds so little security as to be not worth the effort. > > It is also required for secure boot to work AFAIK. Container...

> It'd be good to change rpm-ostree to call out to bootc instead for container operations, instead of directly talking to ostree-ext where possible; this would give us one source...