One thing I think we could probably do here is synthesize distinct tmpfiles.d snippets instead for the subdirectories of /var instead of having the toplevel.
Alternatively...it is tempting here to try to match the semantics of docker volumes, pretend like the base image has VOLUME /var. Then the idea is that the content from the container is only populated on initial deployment - we don't do any tmpfiles.d stuff.
First, we aren't handling hardlinks, see https://github.com/coreos/rpm-ostree/issues/4820
A simple reproducer is
The second problem is that our usage of
C+
in https://github.com/ostreedev/ostree/pull/3103 isn't in c9s systemd.One thing I think we could probably do here is synthesize distinct tmpfiles.d snippets instead for the subdirectories of
/var
instead of having the toplevel.Alternatively...it is tempting here to try to match the semantics of docker volumes, pretend like the base image has
VOLUME /var
. Then the idea is that the content from the container is only populated on initial deployment - we don't do any tmpfiles.d stuff.The more I think about the more I like that.