livecd-rootfs

~xnox/livecd-rootfs:apparmor

  1. Git
  2. lp:~xnox/livecd-rootfs
  3. apparmor
Last commit made on 2020-07-17
Get this branch:
git clone -b apparmor https://git.launchpad.net/~xnox/livecd-rootfs
Only Dimitri John Ledkov can upload to this branch. If you are Dimitri John Ledkov please log in for upload directions.

Branch merges

Branch information

Name:
apparmor
Repository:
lp:~xnox/livecd-rootfs

Recent commits

b14f79c... by Dimitri John Ledkov

apparmor: compile all profiles

31861fd... by Dimitri John Ledkov

seccomp: mount more up-to-date seccomp features

bc4d32a... by Dimitri John Ledkov

seccomp: add more up-to-date seccomp actions

a14a31b... by Dimitri John Ledkov

apparmor: mount more up-to-date apparmor features in the chroot.

37be000... by Dimitri John Ledkov

apparmor: Add generic v5.4 kernel apparmor features

3694cf3... by Dimitri John Ledkov

releasing package livecd-rootfs version 2.675

6e6ab16... by Dimitri John Ledkov

live-server: remove duplicate snaps, due to overlayfs vs snap-preseed.

1ca11c9... by Robert C Jennings

Apply snap-preseed optimizations after seeding snaps

The snap-preseed command can do a number of things during the build
that are currently performed at first boot (apparmor profiles, systemd
unit generation, etc). This patch adds a call to reset the seeding and
apply these optimizations when adding a seeded snap. As a prerequisite
to calling snap-preseed we need to make /dev/mem available as well as
mounts from the host to perform this work, so those are also added here.

2513613... by Steve Langasek

releasing package livecd-rootfs version 2.674

4c504f6... by David Krauser

Fix broken minimal cloud image boot on amd64

I recently pulled initramfs logic out of the base build hook, and
dropped that into the `replace_kernel` function. Any cloud image that
does not leverage the generic virtual kernel was expected to call
`replace_kernel` to pull in a custom kernel. That function will
disable initramfs boot for images that use a custom kernel.

Minimal cloud images on amd64 use the linux-kvm kernel, but the build
hook does not utilize the `replace_kernel` function. Instead, the
kernel flavor is set in `auto/config`. I pulled that logic out of
`auto/config` and am now calling `replace_kernel` in the build hook.

I also moved a call to generate the package list so that it will pick
up the change to the linux-kvm kernel.