'lxd' inteface for 'lxd-terminal'

I’m developing an integration which is a terminal that opens directly into an LXD container that it creates. The idea being that you can you can put developer tools in that container without installing them on your host system. The host system could then, potentially, be read-only as well. To setup the container and to execute a shell in it the snap needs access to LXD. The only container that the program uses is one with the name lxd-terminal-$username (to allow multi-user setups). It does not control, configure or adjust any other containers on the system.

1 Like

+1 from me - the primary purpose of this snap is to utilise lxd and it cannot work without the lxd plug being connected - so consider this +1 for both use-of and auto-connect of lxd for the lxd-terminal snap. Note, since the lxd plug is super-privileged, if granted this will require publisher vetting as well.

+1 too for interface access and auto-connect

It has been one week, so my understanding is that the voting is closed with a +2, which means it passes. Thank you @pfsmorigo and @alexmurray for your votes of confidence.

I’m not sure what “publisher vetting” is, as I can’t find anything about it in any of the published policies, but I’ll try to figure that out next.

+2 votes for, 0 votes against. @advocacy could you please perform publisher vetting? Then we can proceed to grant this for lxd-terminal. Thanks.

@ted What is the official page for lxd-terminal please?

@Igor I haven’t setup a webpage or anything like that, but the Git repo is currently here: https://github.com/ted-gould/lxd-terminal

@ted I don’t really have a good way to verify you based on the data that I have. I don’t doubt your credentials, but given the super-sensitive nature of the this snap, I need more than just the GH repo as the only reference point.

@alexmurray Any suggestions from your side?

Can you link me to the policy document regarding “publisher vetting” so that I can see what options are available? Perhaps there is something I can do there.

@ted If you don’t mind, I will leave that to @alexmurray as the representative of the Store/Security team. Thanks.