Alexander Larsson

@rhatdan Yeah, that sounds good to me. Can we perhaps just add it alwas to our /usr/share/containers/storage.conf file?

@rhatdan Would it maybe be possible instead to have containers/storage fail gracefully when the directory doesn't exist?

So, I've been thinking about the details around this for a while. In particular about the best storage for these additional image directories. The natural approach would be to use...

> > > > https://docs.podman.io/en/v4.2/markdown/podman-play-kube.1.html exists and is usable without an API server. Just for the record, quadlet supports `.kube` files for running play-kube things easily too.

> This one also relates to #165 > > I know at least some people have also been asking for an "apply live by default" mode. Note that there's a...

I like this idea, and it makes sense to have it generalized like this. Some nitpicks: - In the serialized format, i would prefer `!if:all:cond1,cond2` instead of `!if:all:cond1:cond2` - As...

I also worry a bit in general how these stack/merge. Suppose you have an installed app that has `--socket foo --socket-not-if foo:has-bar`, and then you run `flatpak run --socket foo...

Hmm, overall I don't like the proposed syntax as it is a bit double-negative. I think --socket-if with a negation operation is more readable (and allow us non-negated ifs, if...

What I wanted was for --nosocket=foo --socket-if=foo: to reset any previous permissions for socket and make it be more restrictive. But, you're right, this doesn't work if the layer is...

I think we can add a conditional socket option that just means, "clear all previous conditional options" and add that if you --nosocket=foo. That would then not be overridden if...