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 `$ lxc info gold`.
4. in terminal, `$ lxc publish gold/snap0 --alias juju/trusty/amd64`
5. `$ lxc image delete ubuntu-trusty`. This is to delete the default
ubuntu-trusty image downloaded by LXD.
6. Update juju to 2.2.2 (https://jujucharms.com/docs/2.2/reference-install)
7. re-bootstrap a controller (juju bootstrap localhost [pick a name])
It is now using a local image w/ alias `juju/trusty/amd64`.
Thank you Juju.
On 09/01/2017 06:47 AM, Stuart Bishop wrote:
On 1 September 2017 at 02:37, fengxia <fx...@lenovo.com> 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 juju deploy will still download ubuntu-trusty before creating
the container.
I'm attaching the script I'm using, which is slightly modified from
the original version passed around and posted here. It might point you
to where your process is failing. I haven't done it manually myself.
--
Feng xia
Engineer
Lenovo USA
Phone: 5088011794
fx...@lenovo.com
Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
