Enable the installation of snaps in a classic chroot
Bug #1609903 reported by
Dan Watkins
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Won't Fix
|
High
|
Unassigned |
Bug Description
Cloud images are built using livecd-rootfs and then modified for specific clouds by using chroot to modify the contents of the image (without ever booting it).
In order to use snaps to deliver functionality required by clouds on first boot (generally speaking, the agents that they provide), we need some way of installing snaps within these chroots.
Currently, running `snap install ...` within a chroot fails because snapd is (of course) not running.
2016-08-04 17:46:33 slangasek we're going to have a 'snap fetch', I think?
2016-08-04 17:46:53 Odd_Bloke Yeah, I've heard about that in the context of caching a snap for later installation.
2016-08-04 17:47:33 slangasek Odd_Bloke: right. So I think that we may need to do a 'snap fetch', followed by a bit of manual fiddling to put the snap bits in the right place as part of the image build
2016-08-04 17:47:55 slangasek niemeyer: ^^ maybe you'd be able to comment on this problem (pre-installing snaps as part of a classic image build, which happens in a chroot with no running snapd service)