Hi Gustavo,
Thanks for the information! Looking forward to the new release this week!
Peng
On Tue, Dec 13, 2016 at 8:41 PM, Gustavo Niemeyer <
gustavo.nieme...@canonical.com> wrote:
> One detail: note that once your snap goes into the store and passes
> reviews, that issue goes away. Actual us
Hi Gustavo,
Good to hear. Let me also publish this article: [Snappy Interfaces revisit]
https://docs.google.com/document/d/1stvuyn6evk9df7s58ZSAq7g5QOV5gxmWCVqiyEuwDDs/edit?usp=sharing
Feel like the work flow in page 3 need to update after you release the new
snapd. YC
2016-12-14 10:40 GMT+08:0
One detail: note that once your snap goes into the store and passes
reviews, that issue goes away. Actual users of your snap in the wild don't
have to say --dangerous.
On Wed, Dec 14, 2016 at 12:40 AM, Gustavo Niemeyer <
gustavo.nieme...@canonical.com> wrote:
> Hey Peng,
>
> We've overlooked a de
Hey Peng,
We've overlooked a detail in the new interface system which makes it super
inconvenient for you to develop with that interface. We're fixing that in
the release due to go into proposal this week.
Here is the short background, if you're interested: snapd blocks the
connection because it
Already, in the source code (snapd/interfaces/builtin/docker_support.go), I
found the docker-control interface is "reserved". Does that mean
third-party snap can not use it?
On Tue, Dec 13, 2016 at 8:01 PM, Peng Liu wrote:
> Hi Folks,
>
> I am trying to build a snap which needs the permission to
Hi Folks,
I am trying to build a snap which needs the permission to access docker
related system files. I can build the snap successfully with snapcraft, but
when I tried to installed it, the snap command report error "installation
not allowed by "support" plug rule of interface "docker-support"
