Snapd fails to start in my custom ubuntu-core

[Luke Williams]

Wow, I hate typing on my phone. Corrected email below so it actually makes
sense:

One thing I noticed is that if you build your kernel snap with confinement:
strict
It will build your image with the three snaps showing in the snap list
command, so that when you add other snaps, it does not download the
Ubuntu-core snap and make the system 100% unstable.

I've also been using the stable channel instead of edge because with the
edge channel I have not been able to get the device to detect the network
properly on many devices mainly because it's looking for network, and it
being a switch, relies on the network drivers to be loaded before the cloud
init runs which has lead to a boot up time of 5 minutes on initial boot.

On Thursday, September 8, 2016, Luke Williams <luke.williams at canonical.com>
wrote:

> Hi Mike,
>
> One thing I noticed is that if you build your kernel snap with
> confinement: strict
> It will build your image with the three snaps showing in the snap list
> command, so that when you add other snaps, Jr. Does not download the
> Ubuntu-core snap and make the system 100% unstable.
>
> I've also been using the stable channel instead of edge since the edge
> channel I have not been able to get the device to detect the network
> properly on many devices mainly because it's looking for network, and it
> being a switch, relies on the network drivers to be loaded before the cloud
> unit rubs, which has lead to a boot up time of 5 minutes on initial boot.
>
>
> On Thursday, September 8, 2016, MikeB <mabnhdev at gmail.com
> <javascript:_e(%7B%7D,'cvml','mabnhdev at gmail.com');>> wrote:
>
>>
>> I'm looking to run OpenSwitch on several new whitebox switch platforms
>> with Snappy/Ubuntu-Core as the native OS.
>>
>> Each of these platforms requires a custom kernel in order to boot.
>> Each of these platforms requires at least one custom kernel driver to
>> access the network ASIC.
>> Each of these platforms is initially loaded using ONIE.
>>
>> I currently use snapcraft and the kernel plugin to create a custom kernel
>> snap for each platform.  I apply any necessary kernel patches during the
>> pull stage through a custom plugin.  I inject the custom .ko driver files
>> into the parts/kernel/install between the build and stage phases of
>> snapcraft.
>>
>> I then use 'ubuntu-device-flash core 16 --channel=edge --kernel=$snap
>> --gadget=pc --os=ubuntu-core -o $IMG' to create an image.
>>
>> I then use kpartx and ONIE scripts to create an ONIE NOS Installer from
>> the image I created.
>>
>> The most critical problem I have now is that snapd fails to start on my
>> target systems.  No snapd, no snaps.   I assume it is because 'Sep  8
>> 10:56:02 localhost snap[853]: error: cannot read assert seed dir: open
>> /var/lib/snapd/seed/assertions: no such file or directory'.  However, I
>> also see many instances of the following message: 'Sep  8 11:06:34
>> localhost snapd[1689]: error: cannot downgrade: snapd is too old for the
>> current system state (patch level 3)'.
>>
>> Regards, Mike
>>
>
>
> --
> Thanks,
>
>
> Luke Williams - Technical Partner Manager, Network Switches and Ubuntu-Core
> luke.williams at canonical.com
> <javascript:_e(%7B%7D,'cvml','luke.williams at canonical.com');>
> www.canonical.com || www.ubuntu.com
>
>
>

-- 
Thanks,


Luke Williams - Technical Partner Manager, Network Switches and Ubuntu-Core
luke.williams at canonical.com
www.canonical.com || www.ubuntu.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.snapcraft.io/archives/devices/attachments/20160908/49888006/attachment-0001.html>