Thanks Jamie,
I've reopen one [1] that I marked as invalid when I plugged docker-support.
[1] https://bugs.launchpad.net/snappy/+bug/1663175
On 13/02/17 17:04, Jamie Strandboge wrote:
> On Mon, 2017-02-13 at 09:40 -0600, Jamie Strandboge wrote:
>> On Fri, 2017-02-10 at 14:44 +0100, Roberto Mier E
On Mon, 2017-02-13 at 09:40 -0600, Jamie Strandboge wrote:
> On Fri, 2017-02-10 at 14:44 +0100, Roberto Mier Escandón wrote:
> >
> > = Seccomp =
> > Time: Feb 10 12:31:42
> > Log: auid=4294967295 uid=0 gid=0 ses=4294967295 pid=11048 comm="loolkit"
> > exe="/snap/loolwsd/x17/usr/bin/loolforkit" s
On Fri, 2017-02-10 at 14:44 +0100, Roberto Mier Escandón wrote:
> That's interesting, Simon. Good idea having available both $SNAP_DATA
> and /media. We'll do.
>
> But now, let's back to original topic: chroot into snap.
> After solving the issue Thomas found related with the path of the
> docum
That's interesting, Simon. Good idea having available both $SNAP_DATA
and /media. We'll do.
But now, let's back to original topic: chroot into snap.
After solving the issue Thomas found related with the path of the
document, I see now there are two operations not allowed in strict
confinement: mkn
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 ne
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
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
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?
On 10/02/17 08:05, Kyle
On Fri, Feb 10, 2017 at 8:05 AM, Kyle Fazzari
wrote:
>
> On Feb 9, 2017 10:21 PM, "Simon Fels" wrote:
>
> On 09.02.2017 17:08, Thomas Voß wrote:
>> On Thu, Feb 9, 2017 at 2:38 PM, Roberto Mier Escandón
>> wrote:
>>> Because this will use nextcloud documents, and they are internal to
>>> nextcl
On Feb 9, 2017 10:21 PM, "Simon Fels" wrote:
On 09.02.2017 17:08, Thomas Voß wrote:
> On Thu, Feb 9, 2017 at 2:38 PM, Roberto Mier Escandón
> wrote:
>> Because this will use nextcloud documents, and they are internal to
>> nextcloud snap
>>
>
> In that case, content-sharing would help, yes.
I
On 09.02.2017 17:08, Thomas Voß wrote:
> On Thu, Feb 9, 2017 at 2:38 PM, Roberto Mier Escandón
> wrote:
>> Because this will use nextcloud documents, and they are internal to
>> nextcloud snap
>>
>
> In that case, content-sharing would help, yes.
Is that always the case? I thought we talked a
On Thu, Feb 9, 2017 at 2:38 PM, Roberto Mier Escandón
wrote:
> Because this will use nextcloud documents, and they are internal to
> nextcloud snap
>
In that case, content-sharing would help, yes.
> On 09/02/17 14:33, Thomas Voß wrote:
>> I think you want:
>>
>> https://github.com/snapcore/s
Because this will use nextcloud documents, and they are internal to
nextcloud snap
On 09/02/17 14:33, Thomas Voß wrote:
> I think you want:
>
> https://github.com/snapcore/snapd/blob/master/interfaces/builtin/home.go
>
> Why would you need to access documents in other snaps?
>
> On Thu, Feb 9
I think you want:
https://github.com/snapcore/snapd/blob/master/interfaces/builtin/home.go
Why would you need to access documents in other snaps?
On Thu, Feb 9, 2017 at 2:26 PM, Roberto Mier Escandón
wrote:
> awsome Thomas!. You got it!. Having the doc in any snap path can be
> rendered.
>
awsome Thomas!. You got it!. Having the doc in any snap path can be
rendered.
So, that answers the point of chroot working ok, but now there is
another problem: How can I access documents in other snaps? Can content
interface solve this? (I'll try)
On 09/02/17 14:04, Thomas Voß wrote:
> On Thu, Fe
On Thu, Feb 9, 2017 at 11:35 AM, Roberto Mier Escandón
wrote:
>
> Hey Thomas,
>
> You can find the snap at [1]
> Atttached are traces for:
>
> Devmode:
> - service.txt are the logs of the service
> - syslog.txt and snappy-debug.security.txt are the logs to see apparmor
> denials (warnings in thi
Hey Roberto,
On Wed, Feb 8, 2017 at 4:54 PM, Roberto Mier Escandón
wrote:
> Hey engineers,
>
> I need some ideas to solve this: I'm trying to snap collaboraoffice
> online but that's not being easy at all. FYI: this is a kind of Google
> Drive stuff so that when you request in your browser cert
Hey engineers,
I need some ideas to solve this: I'm trying to snap collaboraoffice
online but that's not being easy at all. FYI: this is a kind of Google
Drive stuff so that when you request in your browser certain document,
it is rendered and can be edit by many at the same time, etc..
Though I'
18 matches
Mail list logo
