chroot into a snap

[Simon Fels]

I think you have to support both as otherwise you may miss certain setups
of nextcloud. One may be configured to use $SNAP_DATA/$SNAP_COMMON to store
its data, another one may use /media/.. to do that. In the end there needs
to be some kind of communication happen between both snaps.

Either the nextcloud snap shares the data directory via the content
interface, regardless where it is. However for that case I am not sure if
the security rules of the content interface would allow such a case
(effectively sharing /media to another snap via the content interface).

The other way would be that the nextcloud snap somehow exposes a pointer
for the office snap where to look for its data and then it can either use
the path connected via the content or via the removable-media plug.

regards,
Simon

On Fri, Feb 10, 2017 at 9:48 AM, Roberto Mier Escandón  <
roberto.escandon at canonical.com> wrote:

> Ah, thanks. I'd better use content then.
>
> On 10/02/17 09:38, Simon Fels wrote:
> > On 10.02.2017 09:16, Roberto Mier Escandón  wrote:
> >> I tried content sharing and works fine in this case, Nextcloud exposing
> >> a slot to its documents folder. I think I saw somewhere this is only
> >> valid for a 1-1 plug-slot, so that only 1 snap can use that slot at the
> >> same time. Is that correct? Can removable-media improve this?
> >
> > There can be multiple plugs using the slot.
> >
> > The removable-media interfaces allows access to the host /media
> > directory. That is everything. So unless nextcloud places its data files
> > there this doesn't help you.
> >
> > regards,
> > Simon
> >
> >
>
> --
> Snapcraft mailing list
> Snapcraft at lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20170210/d196a46c/attachment.html>