kendy
commented
4 years ago @kyrofa: Implemented now: https://gerrit.libreoffice.org/c/online/+/96197
With export SNAP_INSTANCE_NAME=nextcloud this now leads to:
lsof | grep 'loolwsd.*unix' | head -n 3 loolwsd 20951 kendy 16u unix 0xffff8802b1e1ec00 0t0 774945 @snap.nextcloud.loolwsd-JelzOF1i@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ type=STREAM loolwsd 20951 kendy 17u unix 0xffff88033ebc5c00 0t0 774946 @snap.nextcloud.loolwsd-JelzOF1i@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ type=STREAM loolwsd 20951 kendy 18u unix 0xffff8802b20ab800 0t0 774947 @snap.nextcloud.loolwsd-JelzOF1i@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ type=STREAM
Hope this is what you need! :-)
kyrofa
timar
gcommit
GabMus
Strit
Extracting the snap-specific discussion from #26. Thanks to @kendy we've made some significant progress in getting this running in the Nextcloud snap. We're not quite there yet, so I wanted to make this issue to track it.
At the moment, the issue is that an abstract unix socket is being created, but abstract sockets need to follow a specific naming pattern in snaps in order to be allowed under confinement (in our case,
@snap.nextcloud.whatever-you-want). I see two ways to make that happen:$SNAP_INSTANCE_NAMEenvironment variable is defined (this is part of the snap standard, and is thus defined for all snaps) and then use@snap.$SNAP_INSTANCE_NAME.as the socket prefix(2) makes for a more generic feature, but I doubt it would be widely-used. As a result, I'm not sure it's worth the effort to make it a generic feature, making (1) perhaps the more attractive option. Any other ideas?