morphis/meta-snappy

Snappy for Yocto/OpenEmbedded

The Yocto support layer has moved to http://github.com/snapcore/meta-snapd

meta-snappy's Issues

Support read-only filesystem

It is often desirable to make the rootfs of a Yocto based image read-only. However for snapd to work "correctly" there are certain paths that must be read-write. In our approach we use OverlayFS for a few mount points, so that the newly installed snaps and their systemd units get written to a persistent "data" partition transparently.

Is that approach "correct" does UbuntuCore use a similar technique as well ?

I think meta-snappy should have a recipe to enable that as well.

building issue yocto for arm 32 bit machine

hello everybody,
I have a problem building yocto with meta-snappy
Build Configuration:
BB_VERSION = "1.36.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-fslc-linux-gnueabi"
MACHINE = "imx6ulevk"
DISTRO = "fslc-framebuffer"
DISTRO_VERSION = "2.4"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "HEAD:9ed1178c87afce997d5a21cadae7461fb6bb48da"
meta-oe
meta-filesystems
meta-multimedia = "HEAD:352531015014d1957d6444d114f4451e241c4d23"
meta-freescale = "HEAD:a4158e3425a79720ddc4c02e76251d567bdceb51"
meta-freescale-3rdparty = "HEAD:a02324e27f7a7ac630dab616f46a8bad7fe2c071"
meta-freescale-distro = "HEAD:51756d1c2058139c8a21f89b86cfd8007b71b7f0"
meta-snappy = "master:0b97a631282b6b8350de10d0265d726e8c7d6f77"
meta-intel = "meta-intel-rocko-2.4:d68dda959b5bf6f90aa8e5c2f027be324bb68e14"

this is the Error:
ERROR: core-image-minimal-snapd-1.0-r0 do_rootfs: Could not invoke dnf. Command '////build/tmp/work/imx6ulevk-fslc-linux-gnueabi/core-image-minimal-snapd/1.0-r0/recipe-sysroot-native/usr/bin/dnf -y -c////build/tmp/work/imx6ulevk-fslc-linux-gnueabi/core-image-minimal-snapd/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=////build/tmp/work/imx6ulevk-fslc-linux-gnueabi/core-image-minimal-snapd/1.0-r0/rootfs/etc/yum.repos.d --repofrompath=oe-repo,////build/tmp/work/imx6ulevk-fslc-linux-gnueabi/core-image-minimal-snapd/1.0-r0/oe-rootfs-repo --installroot=////build/tmp/work/imx6ulevk-fslc-linux-gnueabi/core-image-minimal-snapd/1.0-r0/rootfs --setopt=logdir=////build/tmp/work/imx6ulevk-fslc-linux-gnueabi/core-image-minimal-snapd/1.0-r0/temp --nogpgcheck install packagegroup-snapd snapd rpm apt bash openssh run-postinsts packagegroup-core-boot' returned 1:
Added oe-repo repo from /home/gianpa/fsl-community-bsp/build/tmp/work/imx6ulevk-fslc-linux-gnueabi/core-image-minimal-snapd/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:00 ago on Fri 03 Aug 2018 03:58:09 PM UTC.
Error:
Problem 1: conflicting requests

• nothing provides kernel-module-squashfs needed by snapd-2.32.2-r0.armv7at2hf_neon
  Problem 2: package packagegroup-snapd-1.0-r0.noarch requires snapd, but none of the providers can be installed
• conflicting requests
• nothing provides kernel-module-squashfs needed by snapd-2.32.2-r0.armv7at2hf_neon

ERROR: core-image-minimal-snapd-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: ////build/tmp/work/imx6ulevk-fslc-linux-gnueabi/core-image-minimal-snapd/1.0-r0/temp/log.do_rootfs.13830
ERROR: Task (////sources/meta-snappy/recipes-core/images/core-image-minimal-snapd.bb:do_rootfs) failed with exit code '1'

local.conf:

MACHINE ??= 'imx6ulevk'
DISTRO ?= 'fslc-framebuffer'
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS ??= "
STOPTASKS,${TMPDIR},1G,100K
STOPTASKS,${DL_DIR},1G,100K
STOPTASKS,${SSTATE_DIR},1G,100K
STOPTASKS,/tmp,100M,100K
ABORT,${TMPDIR},100M,1K
ABORT,${DL_DIR},100M,1K
ABORT,${SSTATE_DIR},100M,1K
ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
CONF_VERSION = "1"

DL_DIR ?= "${BSPDIR}/downloads/"
ACCEPT_FSL_EULA = "1"
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""
ROOT_HOME = "/root"
INHERIT += "rm_work"

exclude snapd in case you want to develop snapd recipes

RM_WORK_EXCLUDE += "snapd"
CORE_IMAGE_EXTRA_INSTALL += "openssh"
SSTATE_MIRRORS ?= "
file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n
file://.* file:///some/local/dir/sstate/PATH \n
file://.* http://sstate.yoctoproject.org/dev/PATH;downloadfilename=PATH \n
file://.* http://sstate.yoctoproject.org/2.4/PATH;downloadfilename=PATH \n
file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH \n
"
please help me, I've been trying for the last week but no results

App confinement not working

I tried the demo steps exactly, built rocko, ran with qemu, and tried installing the hello-world snap.

Then I tried the 'hello-world.evil', with the following result:

root@qemux86:~# hello-world.evil
Hello Evil World!
This example demonstrates the app confinement
You should see a permission denied error next
If you see this line the confinement is not working correctly, please file a bug

It asked me to file a bug, so here I am :)

/var/lib/snapd/lib/gl is empty

With opengl interface connected, when I run snap run --shell <my_opengl_connected_snap>, it seems the /var/lib/snapd/lib/gl directory is empty. Is there some service that is missing in our Yocto packaging ?

Ship strict confinement kernel patches by default

This project should, include a bbappend and the required patches to support strict confinement of snapd by default. We currently have patches for QEMU, RaspberryPi and Nvidia Tegra platform already in our fork. https://github.com/crossbario/meta-snappy/tree/master/recipes-kernel/linux

Doesn't build on morty branch

Hi,

Based on the instructions the snapd recipe doesn't build on morty.

| configure: error: "cannot find the rst2man tool, install python-docutils or similar"
| WARNING: /data/poky/build/tmp/work/i586-poky-linux/snapd/2.23.5-r0/temp/run.do_configure.19295:1 exit 1 from 'exit 1'
| ERROR: Function failed: do_configure (log file is located at /data/poky/build/tmp/work/i586-poky-linux/snapd/2.23.5-r0/temp/log.do_configure.19295)
ERROR: Task (/data/poky/meta-snappy/recipes-support/snapd/snapd_2.23.5.bb:do_configure) failed with exit code '1'

Intel Edison Support

The intel edison isn't quite to morty yet, and the projects that support transisitioning are, although not dead, very slow.

Is there a way to get this layer to work on the current intel edison build?

Add snapd-native recipe

We need a snapd-native recipe, the one we can use to run the snap cli tool during the Yocto build process. That can then be used to "seed" snaps during image build process.

We have a recipe already created that we use internally. Will propose that here once #36 lands

Include a recipe to "seed" snaps

When someone is building a Yocto based system, they need to ship a few snaps by default as well.

To enable that, one needs a statically built snapd to run CLI commands, we also need to be able to define an environment variable that could be set in local.conf that our recipe would pick to "seed" snap packages by default.

Please update to latest snapd

We are looking to use meta-snappy layer to add snap support in our project. It seems snapd is not at the latest version currently.

Kindly update to the latest version.

Go packages in the layer and meta-golang layer

At the moment, this layer brings its own cross Go recipes along with some Go package recipes. This conflicts with meta-golang if one tries to use both. IMO, it would be better to use that layer as a dependency, since it's well-maintained, has recipes for Go itself (and nice golang class to ease cross-compilation of Go recipes) and has some of snapd package dependencies already.

Had this been considered? Are there any plans to do that?

Build snaps from existing recipes

Hey all,
is this layer also capable of building snaps from existing recipes, so they get build with the image? Or is it just containing the "runtime" to install/uninstall snaps.

Thanks