I used: lxd-images import ubuntu trusty amd64 --sync --alias ubuntu-trusty
Which I stole from Jorge's blog. bugg@tomsdevbox:~$ lxc image list +----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+ | ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE | +----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+ | ubuntu-precise | 4029ee764a39 | no | Ubuntu 12.04 LTS server (20160222) | x86_64 | 155.25MB | Feb 26, 2016 at 5:12pm (CET) | | ubuntu-trusty | 510c27eb5e30 | no | Ubuntu 14.04 LTS server (20160222) | x86_64 | 118.51MB | Feb 26, 2016 at 5:13pm (CET) | | ubuntu-wily | fb2cf6ab4af1 | no | Ubuntu 15.10 server (20160222) | x86_64 | 154.27MB | Feb 26, 2016 at 5:12pm (CET) | +----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+ -------------- Director Meteorite.bi - Saiku Analytics Founder Tel: +44(0)5603641316 (Thanks to the Saiku community we reached our Kickstart <http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/> goal, but you can always help by sponsoring the project <http://www.meteorite.bi/products/saiku/sponsorship>) On 27 February 2016 at 12:14, John Meinel <j...@arbash-meinel.com> wrote: > What image did you import into LXD? You should use something like: > lxd-images import ubuntu trusty --alias ubuntu-trusty > > (substitute xenial/wily etc as relevant.) > > That looks like you are using an image from linuxcontainers.org which is > very different from the ones built by cloud-images.ubuntu.com > > John > =:-> > > > On Sat, Feb 27, 2016 at 4:09 PM, Tom Barber <t...@analytical-labs.com> > wrote: > >> Thanks John >> >> That was sort of my thinking too. But it's not a groups thing that I can >> see. Same issue as root or as unprivileged users. >> >> >> bugg@tomsdevbox:~$ groups >> >> bugg lxd >> >> bugg@tomsdevbox:~$ lxd --version >> 2.0.0.beta2 >> >> >> bugg@tomsdevbox:~$ lxc --version >> 2.0.0.beta2 >> >> >> at which point the bootstrap trust image starts fine, and i can >> >> lxc exec juju-...... /bin/bash >> >> into it. But sshd isn't running which explains why the connection refused >> error appears. >> >> Tom >> >> On 27 Feb 2016 11:56, "John Meinel" <j...@arbash-meinel.com> wrote: >> >>> Connection refused isn't the error you would be getting if it was the >>> current incompatibilities. What you're seeing looks more like you aren't in >>> the "LXD" group, or you didn't refresh your groups after installing LXD. >>> (newgrp lxd) >>> >>> John >>> =:-> >>> >>> >>> On Sat, Feb 27, 2016 at 12:08 AM, Tom Barber <t...@analytical-labs.com> >>> wrote: >>> >>>> No worries Serge I was just some Friday fun to get me out of the daily >>>> grind. Thanks for the update. >>>> >>>> Tom >>>> On 26 Feb 2016 8:02 pm, "Serge E. Hallyn" <se...@hallyn.com> wrote: >>>> >>>>> On Fri, Feb 26, 2016 at 02:42:51PM +0000, Tom Barber wrote: >>>>> > Afternoon, got bored decided to try Jorge's blog post about Juju LXD >>>>> and ZFS >>>>> > >>>>> > I'd read on a few posts about the requirement for LXD beta2 because >>>>> of API >>>>> > incompatibilities so I found the deb's and installed them. >>>>> > >>>>> > Its up and running and images start fine, but juju bootstrap fails >>>>> with >>>>> > connection refused when trying to SSH in. Something stupid i'm doing >>>>> or >>>>> > just broke for now? >>>>> >>>>> Hi Tom, >>>>> >>>>> Yeah it's just broken for now. It will be fixed when a new feature >>>>> branch >>>>> is merged, which I think is supposed to happen on or before Monday. >>>>> >>>>> -serge >>>>> >>>> >>>> -- >>>> Juju mailing list >>>> Juju@lists.ubuntu.com >>>> Modify settings or unsubscribe at: >>>> https://lists.ubuntu.com/mailman/listinfo/juju >>>> >>>> >>> >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
