Re: How to use LXC local image for new machine

To give an update on this, and it can be helpful to someone interested in: Verified. 1. create a vanilla `trusty` LXD container named `gold` 2. ssh into `gold` container, `apt install python python-dev...` 3. in terminal, `$ lxc snapshot gold`, this created a snapshot, can be viewed from `$

Re: How to use LXC local image for new machine

If you're seeing "ubuntu-trusty" then you're using a version of Juju that doesn't support the pressed. I believe reusing the cached image first was added in 2.1, when we switched the naming scheme to be more specific. John =:-> On Sep 1, 2017 18:10, "Alex Kavanagh"

Re: How to use LXC local image for new machine

On Fri, Sep 1, 2017 at 11:47 AM, Stuart Bishop wrote: > On 1 September 2017 at 02:37, fengxia wrote: > > According to https://bugs.launchpad.net/juju/+bug/1650651, juju 2.1 > supports > > using local image if its alias is `juju/series/arch` format.

Re: How to use LXC local image for new machine

On 1 September 2017 at 02:37, fengxia wrote: > According to https://bugs.launchpad.net/juju/+bug/1650651, juju 2.1 supports > using local image if its alias is `juju/series/arch` format. > > So following this, I created a local image and gave it an alias of this > format, but

Re: How to use LXC local image for new machine

According to https://bugs.launchpad.net/juju/+bug/1650651, juju 2.1 supports using local image if its alias is `juju/series/arch` format. So following this, I created a local image and gave it an alias of this format, but juju deploy will still download ubuntu-trusty before creating the

How to use LXC local image for new machine

Hi Juju, I'm using `localhost` provider for dev test. I have create a LXD controller, and each time `juju deploy` will create a new container (series/trusty). I'm experimenting to use a local image so `juju deploy` can use. So far: 1. Created an image, "gold-copy" 2. `lxc image alias