This is an active discussion for us at the moment, I think we will have
a solution for you soon.
Mark
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
Hi,
I would think that the security concerns can be minimized, if not
completely eliminated, by setting up a way to have one snap application
invoke another, possibly itself. In theory, a snap itself is already
vetted and running in a secure environment. So what's insecure about one
snap asking
Hey guys,
With our Rocket.Chat server snap. We've had several cases now where users
come to us trying to figure out why it hasn't started yet after installing.
Our snap:
https://github.com/RocketChat/Rocket.Chat/blob/develop/.snapcraft/stable/snapcraft.yaml
rocketchat-mongo:
command: env
On Tue, Oct 18, 2016 at 4:48 AM, Loïc Minier wrote:
> Hi!
>
> Docker is since some days available as a properly confined snap. This will
> work on top of classic Ubuntu 16.04+ or on top of an up-to-date Ubuntu Core
> series 16.
Nice work :-)
> Because the docker.sock
Hi,
The Snappy team is happy to announce the Release Candidate of Ubuntu
Core 16.
Ubuntu Core is an operating system entirely based on snaps, including
its foundation. Applications, kernel, core operating system, and
gadget components are all managed as snaps and are installed and
refreshed by
On Thu, Oct 20, 2016 at 8:18 PM, Dustin Kirkland
wrote:
> > Because the docker.sock path is hardcoded in a lot of images, this snap
> > conflicts with docker debs, so make sure you remove them first:
> > sudo apt purge docker docker-engine
>
> Hmm, that feels like