My understanding is that the interface will be updated to create ~/.local/share for us if it doesn't exist, so that juju itself can create ~/.local/share/juju.
I think it makes sense to have the confinement such that juju itself cannot create ~/.local/share (it shouldn't be able to muck around in any other directories in that path).
The short term workaround is to add a "mkdir -p ~/.local/share" in your CI scripts, but that doesn't work very well for arbitrary end users.
My understanding is that the interface will be updated to create ~/.local/share for us if it doesn't exist, so that juju itself can create ~/.local/ share/juju.
I think it makes sense to have the confinement such that juju itself cannot create ~/.local/share (it shouldn't be able to muck around in any other directories in that path).
The short term workaround is to add a "mkdir -p ~/.local/share" in your CI scripts, but that doesn't work very well for arbitrary end users.