Autodetecting whether or not to persist the journal from the presence of /var/log/journal conflicts with the "factory reset" logic as implemented by ostree (/var/ starts out empty).
We're currently carrying
https://pagure.io/fedora-atomic/blob/37389c874240db4055c8076600a89a5fa3eba4a7/f/treecompose-post.sh#_6
and while this one-liner is not a huge burden, I'm trying to track our downstream workarounds and continually approach the ideal of having the base RPMs work without tweaking.
My suggestion here is an upstream flag like --enable-journal-storage-default=persistent that we set in the spec.
Comment 1Zbigniew Jędrzejewski-Szmek
2017-01-18 19:01:53 UTC
Yeah, I think the time has come to do something like this. I think we might event want to do this upstream.
Comment 2Zbigniew Jędrzejewski-Szmek
2025-11-07 15:03:35 UTC