[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** 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 Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Invalid Status in lxc-android-config package in Ubuntu: Won't Fix Status in urfkill package in Ubuntu: Won't Fix Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. apply changes from https://code.launchpad.net/~vicamo/lxc-android- config/lxd-migration/+merge/311103 . This cause the system to automatically import android initrd as an lxd image and to start it up on boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical-devices- system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto - 4. run lxd image create script to create the android lxd image. - - $ ./lxd-image-create.sh - - 5. create an ephemeral container for debug: - - $ lxc init -e -p android android armhf - $ lxc start armhf + 4. apply changes from https://code.launchpad.net/~vicamo/lxc-android- + config/lxd-migration/+merge/311103 . This cause the system to + automatically import android initrd as an lxd image and to start it up + on boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Status in urfkill package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. apply changes from https://code.launchpad.net/~vicamo/lxc-android- config/lxd-migration/+merge/311103 . This cause the system to automatically import android initrd as an lxd image and to start it up on boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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 Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Status in urfkill package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** Also affects: urfkill (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Status in urfkill package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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 bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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 my kernel merge proposal. ** Attachment removed: "boot.img" https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777591/+files/boot.img -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** 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 Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
AppArmor is not functioning this way Hmmm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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 Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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. I/UpstartPropertyWatcher( 1833): Property changed: init.svc.logd=running E/libaudit(30123): Error sending data over the netlink socket: Unknown error -111 E/libaudit(30123): Could net set pid for audit events, error: Connection refused I/UpstartPropertyWatcher( 1833): Property changed: init.svc.logd=restarting -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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 launching lxd container via `lxc launch -e ...`, but it would be nice if that's somehow covered by lxd daemon. Don't know if it's possible to create an ephemeral yet autostart container in a formal way. 3. wifi/bluetooth is not available at boot because urfkill starts before the container. Need a manual restart to urfkill. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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" https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777978/+files/lxd-image-create.sh ** 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical-devices- system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. - 5. edit lxd profile manually because it doesn't currently support - setting multiple entries of "raw.lxc" config: + $ ./lxd-image-create.sh - $ lxc profile edit android - # This should bring up an editor, default nano. Use - # `update-alternatives --config editor` to choose the one you like. - # The result should be: - $ lxc profile show android - name: android - config: - raw.lxc: | - lxc.devttydir=lxc - lxc.tty=4 - lxc.cap.drop=mac_admin mac_override - lxc.aa_profile=unconfined - lxc.autodev=0 - lxc.init_cmd=/init - lxc.cgroup.devices.allow = a - lxc.mount.auto= - lxc.mount.auto=sys:rw proc:mixed cgroup:mixed - security.nesting: "true" - security.privileged: "true" - description: "" - devices: - dev_socket: - path: /dev/socket - source: /dev/socket - type: disk - - 6. create an ephemeral container for debug: + 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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. lxc.cgroup.devices.allow = a lxc.mount.auto= lxc.mount.auto=sys:rw proc:mixed cgroup:mixed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init lxc.cgroup.devices.allow = a lxc.mount.auto= lxc.mount.auto=sys:rw proc:mixed cgroup:mixed security.nesting: "true" security.privileged: "true" description: "" devices: dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical-devices- system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init + lxc.cgroup.devices.allow = a + lxc.mount.auto= + lxc.mount.auto=sys:rw proc:mixed cgroup:mixed security.nesting: "true" security.privileged: "true" description: "" devices: - dev_binder: - path: /dev/binder - type: unix-char dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init lxc.cgroup.devices.allow = a lxc.mount.auto= lxc.mount.auto=sys:rw proc:mixed cgroup:mixed security.nesting: "true" security.privileged: "true" description: "" devices: dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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 because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init security.nesting: "true" security.privileged: "true" description: "" devices: dev_binder: path: /dev/binder type: unix-char dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** 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 tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical-devices- system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). - $ lxd init --auto + $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init security.nesting: "true" security.privileged: "true" description: "" devices: dev_binder: path: /dev/binder type: unix-char dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init security.nesting: "true" security.privileged: "true" description: "" devices: dev_binder: path: /dev/binder type: unix-char dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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 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., * migrate systemd service definitions, etc. + + [Steps to reproduce current setup] + 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 + 1. add /var/lib/lxd to writable paths + 2. install lxd, lxd-client and then reboot the device so that writable path may take effect. + 3. initialize lxd. This can take a while (2 minutes for me). + + $ lxd init --auto + + 4. run lxd image create script to create the android lxd image. + 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: + + $ lxc profile edit android + # This should bring up an editor, default nano. Use + # `update-alternatives --config editor` to choose the one you like. + # The result should be: + $ lxc profile show android + name: android + config: + raw.lxc: | + lxc.devttydir=lxc + lxc.tty=4 + lxc.cap.drop=mac_admin mac_override + lxc.aa_profile=unconfined + lxc.autodev=0 + lxc.init_cmd=/init + security.nesting: "true" + security.privileged: "true" + description: "" + devices: + dev_binder: + path: /dev/binder + type: unix-char + dev_socket: + path: /dev/socket + source: /dev/socket + type: disk + + 6. create an ephemeral container for debug: + + $ lxc init -e -p android android armhf + $ lxc start armhf ** Attachment added: "boot.img" https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777591/+files/boot.img ** 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] - 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 - 1. add /var/lib/lxd to writable paths - 2. install lxd, lxd-client and then reboot the device so that writable path may take effect. + + 0. rebuild avila kernel with additional patches from + https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 + + 1. follow bug 1641505 and https://bugs.launchpad.net/canonical-devices- + system-image/+bug/1641505/comments/2 to enable adbd emergency mode and + disable current lxc-based android container. + + 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and + then reboot the device so that writable path may take effect. + 3. initialize lxd. This can take a while (2 minutes for me). - $ lxd init --auto + $ lxd init --auto 4. run lxd image create script to create the android lxd image. - 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: - $ lxc profile edit android - # This should bring up an editor, default nano. Use - # `update-alternatives --config editor` to choose the one you like. - # The result should be: - $ lxc profile show android - name: android - config: - raw.lxc: | - lxc.devttydir=lxc - lxc.tty=4 - lxc.cap.drop=mac_admin mac_override - lxc.aa_profile=unconfined - lxc.autodev=0 - lxc.init_cmd=/init - security.nesting: "true" - security.privileged: "true" - description: "" - devices: - dev_binder: - path: /dev/binder - type: unix-char - dev_socket: - path: /dev/socket - source: /dev/socket - type: disk + 5. edit lxd profile manually because it doesn't currently support + setting multiple entries of "raw.lxc" config: + + $ lxc profile edit android + # This should bring up an editor, default nano. Use + # `update-alternatives --config editor` to choose the one you like. + # The result should be: + $ lxc profile show android + name: android + config: + raw.lxc: | + lxc.devttydir=lxc + lxc.tty=4 + lxc.cap.drop=mac_admin mac_override + lxc.aa_profile=unconfined + lxc.autodev=0 + lxc.init_cmd=/init + security.nesting: "true" + security.privileged: "true" + description: "" + devices: + dev_binder: + path: /dev/binder + type: unix-char + dev_socket: + path: /dev/socket + source: /dev/socket +
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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 are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 1. add /var/lib/lxd to writable paths 2. install lxd, lxd-client and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init security.nesting: "true" security.privileged: "true" description: "" devices: dev_binder: path: /dev/binder type: unix-char dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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 Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** 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 Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** Changed in: canonical-devices-system-image Milestone: None => x1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
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 https://github.com/lxc/lxd/issues/2039 . At lease commit 160da84 "userns: Allow PR_CAPBSET_DROP in a user namespace" has to be cherry- picked, but besides that, I also found a lot similar places to be fixed. ** Bug watch added: LXD bug tracker #2039 https://github.com/lxc/lxd/issues/2039 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: 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., * migrate systemd service definitions, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
