Hi, I wanted to capture one of the issues that was encountered.
ubuntu-device-flash snap can not work from an Ubuntu Core system; this is because it calls kpartx with the -s flag which relies on libdevmapper coordinating with its udev counterpart. Because dmsetup isn't installed in the core image, the udev signaling never comes back. To sum up: - Ubuntu classic + kpartx -avs: works - Ubuntu Core + kpartx -avs: hangs - Ubuntu Core + kpartx -av: works I wanted to mention this for people who try running ubuntu-device-flash from an Ubuntu Core system. (Various workarounds would be possible but because ubuntu-device-flash ought to be replaced by ubuntu-image soon it's probably not worth addressing right now.) Cheers, - Loïc Minier On Wed, Aug 31, 2016 at 8:27 PM, Loïc Minier <[email protected]> wrote: > Yep; but the failure in kpartx didn't seem specific to local vs remote > snaps. > > For people on the list, I followed up on IRC and Yann was running into > weird issues with kpartx and ext4 in his environments, but from a clean > Ubuntu vm things worked and that's a viable solution for now. > > Cheers, > - Loïc > > On Wed, Aug 31, 2016 at 12:26 PM, Simon Fels <[email protected]> > wrote: > >> On 31.08.2016 12:16, Loïc Minier wrote: >> > Works for me: >> > >> > $ sudo -E UBUNTU_DEVICE_FLASH_IGNORE_UNSTABLE_GADGET_DEFINITION=1 >> > /snap/bin/ubuntu-device-flash --verbose core 16 -o snappy.img --channel >> > edge --gadget pc --kernel pc-kernel --os ubuntu-core >> >> Yann is trying to use a gadget snap which isn't in the store but placed >> on the local disk. So I suspect he is running something like >> >> $ sudo -E UBUNTU_DEVICE_FLASH_IGNORE_UNSTABLE_GADGET_DEFINITION=1 >> /snap/bin/ubuntu-device-flash ... --gadget /home/user/my-gadget.snap ... >> >> regards, >> Simon >> >> > Determining gadget configuration >> > >> > 836.00 KB / 836.00 KB [==================================] 100.00% >> > 12.77 MB/s 0 >> > >> > Partitioning... >> > >> > Formatting... >> > >> > Mounting... >> > >> > Provisioning... >> > >> > 74.40 MB / 74.40 MB [===================================] 100.00% >> 24.02 >> > MB/s 3s >> > >> > 74.40 MB / 74.40 MB [===================================] 100.00% >> 59.46 >> > MB/s 1s >> > >> > 110.54 MB / 110.54 MB [=================================] 100.00% >> 23.19 >> > MB/s 4s >> > >> > 836.00 KB / 836.00 KB [==================================] 100.00% >> > 68.23 MB/s 0 >> > >> > Unmounting... >> > >> > New image complete >> > >> > Summary: >> > >> > Output: snappy.img >> > >> > Architecture: amd64 >> > >> > Channel: edge >> > >> > Version: 0 >> > >> > >> > On Wed, Aug 31, 2016 at 11:11 AM, Yann Sionneau >> > <[email protected] <mailto:[email protected]>> wrote: >> > >> > >> > >> > Le 08/31/2016 à 10:56 AM, Simon Fels a écrit : >> > > On 31.08.2016 10:49, Yann Sionneau wrote: >> > >> Hello, >> > >> >> > >> It seems the new (snapp'ed) ubuntu-device-flash cannot use my >> own gadget >> > >> snap anymore. >> > >> >> > >> yann@imperium$ sudo -E /snap/bin/ubuntu-device-flash --verbose >> core 16 >> > >> -o snappy.img --channel edge --gadget >> $PWD/../../../xxx_2.0_all.snap >> > >> --kernel ../../../xxx_kernel/xxx-kernel_3.10.97_armhf.snap --os >> > >> ubuntu-core --developer-mode --enable-ssh >> > >> cannot use >> > >> "/home/yann/dev/snappy_xxx/tools/snappy/xxx_image/../../../ >> xxx_2.0_all.snap", >> > >> must be one of: ["canonical-i386" "canonical-pc" "pc" >> "canonical-pi2" >> > >> "pi2" "pi3" "canonical-dragon" "dragonboard" "beagleblack" >> "plano-amd64"] >> > >> >> > >> Is porting Snappy on non official devices not supported anymore? >> > > No, that is not the case. >> > > >> > >> How is it supposed to work now? I must confess that I am blocked >> in my >> > >> work because of this change, I cannot generate nor flash images >> anymore >> > >> and my project is thus stalled :/ >> > > We're currently in a phase where ubuntu-device-flash is still >> being used >> > > but the future will be a new tool called ubuntu-image which will >> allow >> > > you to create images in a much better way. >> > Yes I've heard of the new ubuntu-image tool. It's a good idea to >> make >> > this new tool! >> > It's just important I think that the old tools stay functional >> until the >> > new ones are ready. >> > > >> > > From what I got from Michael a lot things are currently hard coded >> > > inside ubuntu-device-flash. See [1] for the relevant code bits. >> > > >> > > You can override the sanity check for the gadget names with >> setting >> > > UBUNTU_DEVICE_FLASH_IGNORE_UNSTABLE_GADGET_DEFINITION=1 in the >> command >> > > line you're executing. Didn't tested this but maybe Michael can >> comment >> > > how this should work. >> > Ok, the environment variable works, thanks a lot! >> > Now I get this: >> > >> > error while executing external command mkfs.ext4 -F -L writable >> > /dev/mapper/loop3p2: mke2fs 1.42.13 (17-May-2015) >> > Invalid filesystem option set: >> > has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,di >> r_nlink,extra_isize >> > >> > any idea? >> > >> > > >> > > regards, >> > > Simon >> > > >> > > [1]: >> > > >> > https://bazaar.launchpad.net/~mvo/goget-ubuntu-touch/minima >> l-first-boot-no-prepare-image/view/head:/ubuntu-device- >> flash/snappy.go#L116 >> > <https://bazaar.launchpad.net/~mvo/goget-ubuntu-touch/mi >> nimal-first-boot-no-prepare-image/view/head:/ubuntu-device- >> flash/snappy.go#L116> >> > > >> > >> > >> > -- >> > Snapcraft mailing list >> > [email protected] <mailto:[email protected]> >> > Modify settings or unsubscribe at: >> > https://lists.ubuntu.com/mailman/listinfo/snapcraft >> > <https://lists.ubuntu.com/mailman/listinfo/snapcraft> >> > >> > >> > >> > >> > -- >> > - Loïc >> > >> > >> >> >> -- >> Snapcraft mailing list >> [email protected] >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >> an/listinfo/snapcraft >> > > > > -- > - Loïc > -- - Loïc
-- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
