** Changed in: urfkill (Ubuntu)
Status: New => Won't Fix
** Changed in: lxc-android-config (Ubuntu)
Status: New => Won't Fix
** Changed in: canonical-devices-system-image
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
Several things to do here:
* include lxd, lxd-client in default installation,
* writable path for lxd: lxd resides at /var/lib/lxd and it takes write
permission to fully function,
* migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles,
etc.,
All known issues in comment 8 addressed, so I think that's all we need
for lxd porting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc android container to lxd
To manage
** Also affects: urfkill (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc android container to lxd
To manage
Update prebuilt boot.img with current kernel changes in
https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
** Attachment added: "boot.img"
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4778450/+files/boot.img
--
You received this
audit namespace issue fixed in upstream
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f9441639e6319f0c0e12bd63fa2f58990af0a9d2
and
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=33faba7fa7f2288d2f8aaea95958b2c97bf9ebfb
. Already included in
** Branch linked: lp:~vicamo/lxc-android-config/lxd-migration
** Branch unlinked: lp:~vicamo/lxc-android-config/lxd-writable-path
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
Add audit=0 to kernel command line and logd ceases to try kernel audit,
and the rest of the system (lxd/snap) doesn't seem to be affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
AppArmor is not functioning this way Hmmm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc android container to lxd
To manage notifications about this bug go to:
Another issue seems to relate to the kernel version again. In logcat
messages I found logd restarts over and over again due to failure when
sending audit netlink messages. It seems lxd fails to setup some
cgroups: cgroups controllers for blkio/memory/network/pids/... not
found.
With some hacking with systemd, now lxd image boots and GUI is
available. Some refinements are needed. Known issues:
1. lxc tries to write client.srt to /root/.config/lxc, which should be
read-only by default. Add --force-local to every lxc command invoked
fixes this issue.
2. Currently I'm
Script to generate android lxd image from /android/system/boot/android-
ramdisk.img
** Attachment removed: "lxd-image-create.sh"
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777635/+files/lxd-image-create.sh
** Attachment added: "lxd-image-create.sh"
Current status: with following three lines added to the profile, ueventd
processes devices as usual. But I can't still found any daemon process
with executable located in /system running. /proc/$(pidof init)/mounts
shows /system and all other partitions have been correctly mounted.
** Description changed:
Several things to do here:
* include lxd, lxd-client in default installation,
* writable path for lxd: lxd resides at /var/lib/lxd and it takes write
permission to fully function,
* migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles,
etc.,
Script to generate android lxd image from /android/system/boot/android-
ramdisk.img
** Attachment added: "lxd-image-create.sh"
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777635/+files/lxd-image-create.sh
--
You received this bug notification
** Branch linked: lp:~vicamo/lxc-android-config/lxd-writable-path
** Description changed:
Several things to do here:
* include lxd, lxd-client in default installation,
* writable path for lxd: lxd resides at /var/lib/lxd and it takes write
permission to fully function,
* migrate lxc
Prebuilt boot image with
https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
applied.
** Merge proposal linked:
https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
** Description changed:
Several things to do here:
* include lxd, lxd-client in
Again, the fundermental reason init dies is a critical core service
healthd dies, so it's not really about background/foreground here. And
healthd dies because it fails to open /dev/binder. It follows in lxd,
ueventd is not correctly running yet.
--
You received this bug notification because you
With comment #1 fixed with a patched kernel, it seems we bumped into bug
1625916 again. Need to run lxc in the background.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Vicamo Yang (vicamo)
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: canonical-devices-system-image
Milestone: None => x1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc android container to lxd
To manage notifications
Again, avila's kernel is pretty outdated, and its user namespace support
is so poor that it's actually mis-behave on a certain security related
operations.
In security/commoncap.c, function cap_prctl_drop, it should check
`ns_capable(...)`, not just `capable(...)`. See
22 matches
Mail list logo
