"juju show-machine 10" is likely to tell you why we are failing to provision the machine.
My guess is that we acctually need the alias to be "juju/centos7/amd64" for Juju to recognize that it is the container image we want to be starting. John =:-> On Thu, Jun 15, 2017 at 8:37 PM, Daniel Bidwell <drbidw...@gmail.com> wrote: > I am trying to deploy a charm that I am writing for both ubuntu and > centos. "lxc image alias list" produces: > > lxc image alias list > +-------------------+--------------+-------------------+ > | ALIAS | FINGERPRINT | DESCRIPTION | > +-------------------+--------------+-------------------+ > | centos7 | 41c7bb494bbd | centos7 | > +-------------------+--------------+-------------------+ > | juju/xenial/amd64 | 1e59027d1d58 | juju/xenial/amd64 | > +-------------------+--------------+-------------------+ > | ubuntu-xenial | 1e59027d1d58 | ubuntu-xenial | > +-------------------+--------------+-------------------+ > > "juju deploy ~/charms/xenial/aubase1 --series centos7 aubasecentos" > looks like it is starting, but a "juju status" produces: > > juju status > Model Controller Cloud/Region Version > default lxd-test localhost/localhost 2.1.2 > > App Version Status Scale Charm Store Rev OS Notes > aubase1 active 1 aubase1 local 5 ubuntu > aubasecentos waiting 0/1 aubase1 local 4 centos > > Unit Workload Agent Machine Public > address Ports Message > aubase1/4* active idle 9 10.130.54.192 > aubasecentos/4 waiting allocating 10 waiting > for machine > > Machine State DNS Inst id Series AZ > 9 started 10.130.54.192 juju-a0c4c9-9 xenial > 10 down pending centos7 > > What do I need to do to deploy a centos lxd container with my charm? > -- > Daniel Bidwell <drbidw...@gmail.com> > > > -- > 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
