[NEWS] Altoros (Cloud Foundry) using Snaps

https://blog.altoros.com/how-to-use-snap-packages-when-collecting-iot-data-with-predix-time-series.html "Judging from our experience with snaps, developing, as well as publishing, them is quite easy, and the process is supported by good enough documentation." -- Michael Hall mhall...@ubuntu.com

Re: core_383.snap missing after reboot of Ubuntu-Core

Glad you figured it out. Note that the behavior of removing the snap from the original seed was actually a bug we already fixed. The stable image will be out very soon, and has that problem as well as many others properly fixed. On Wed, Nov 2, 2016 at 9:21 PM, Luke Williams

Re: core_383.snap missing after reboot of Ubuntu-Core

Figured it out with the help of community. It was due to my kernel snap having a specific name in my assertion and it was causing the core snap to remove itself after failed boot. I had to give the assertion model the generic “name” of my kernel snap and then point the actual kernel snap file

Re: Problem removing a snap

On Wed, 2016-11-02 at 16:57 -0600, Seth Arnold wrote: > On Wed, Nov 02, 2016 at 05:34:10PM -0500, Chris wrote: > > > > chris@localhost:~$ sudo mount --bind /snap/ubuntu-core/current > > /snap/viking-gps/1 > > [sudo] password for chris:  > > mount: mount point /snap/viking-gps/1 does not exist >

Re: Problem removing a snap

On Wed, Nov 02, 2016 at 05:34:10PM -0500, Chris wrote: > chris@localhost:~$ sudo mount --bind /snap/ubuntu-core/current > /snap/viking-gps/1 > [sudo] password for chris:  > mount: mount point /snap/viking-gps/1 does not exist Either a file or directory needs to exist in the filesystem for a mount

Re: Problem removing a snap

On Wed, 2016-11-02 at 20:40 -0200, Gustavo Niemeyer wrote: > > There's no need to attempt to remove again. snapd has proper state > tracking and still remembers that you are trying to remove that snap. > > If you kept the directory mounted as suggested, by now it should > already be gone. > I'd

Re: Problem removing a snap

There's no need to attempt to remove again. snapd has proper state tracking and still remembers that you are trying to remove that snap. If you kept the directory mounted as suggested, by now it should already be gone. On Wed, Nov 2, 2016 at 8:34 PM, Chris wrote: > On

Re: Problem removing a snap

On Wed, 2016-11-02 at 20:06 -0200, Gustavo Niemeyer wrote: > Ok, thanks for those details. We'll look more deeply into this > tomorrow and try to reproduce the issue. > > To fix your problem, can you please try this simple hack to get over > the bug: > > sudo mount --bind

Re: Problem removing a snap

Ok, thanks for those details. We'll look more deeply into this tomorrow and try to reproduce the issue. To fix your problem, can you please try this simple hack to get over the bug: sudo mount --bind /snap/ubuntu-core/current /snap/viking-gps/1 This should allow the remove to go through. On

Re: Problem removing a snap

Hi Chris, Can you please try updating your snapd package? Recent releases have a more reliable remove procedure that handles these cases better. On Wed, Nov 2, 2016 at 6:40 PM, Chris wrote: > I went to remove a snap, viking-gps, and it just sat there doing > nothing.

Problem removing a snap

I went to remove a snap, viking-gps, and it just sat there doing nothing. I did a CTRL-C to stop the process. So, running snap changes showed me 343  Doing   2016-11-02T17:22:13Z  - Remove "viking-gps" snap Then running snap change 343, since it was still running I get:

Re: Snap Shadowsocks and publish it to the Ubuntu Store

Yo, looks like a good tutorial for Chinese devs~  2016-11-02 17:36 GMT+08:00 XiaoGuo Liu : > Hi, > > Today, I created a tutorial about how to snap shadowsocks and publish it > into Ubuntu Store. > > Tutorial: 如何snap Shadowsocks并发布到Ubuntu Store >

Re: Optional daemon

On 11/02/2016 12:41 AM, Didier Roche wrote: > Le 28/10/2016 à 21:00, Aaron Ogle a écrit : >> Point definitely well made. I'm with you now. :) >> >> Now this being the case. I can't just swap the location. This is >> where I would need a rock solid upgrade hook. But I would only need >> to run

Re: Optional daemon

Le 28/10/2016 à 21:00, Aaron Ogle a écrit : > Point definitely well made. I'm with you now. :) > > Now this being the case. I can't just swap the location. This is > where I would need a rock solid upgrade hook. But I would only need > to run it the once. Any suggestions? Or any good