Stuck on Starting container... since upgrade to precise :(

[Serge E. Hallyn]

Quoting Kapil Thangavelu (kapil.thangavelu at canonical.com):
> Excerpts from Serge E. Hallyn's message of 2012-05-02 05:32:41 -0700:
> > Quoting Luis Arias (kaaloo at gmail.com):
> > > Hi,
> > > 
> > > I found that C:\nppdf32Log\debuglog.txt file in my home dir and deleted it.
> > >  Googling around it seems this file is created by Adobe Reader.  Anyhow, I
> > > cleared as many caches as I could find  ~/.juju/cache, /var/cache/lxc,
> > 
> > I don't understand.  What is your host system, that on which you are
> > running juju?  How does it find a 'C:'?
> > 
> > > /var/cache/apt-cacher-ng and the juju local dir but that setting keeps
> > > coming up in the unit's container config.  I can't seem to get rid of it.
> > > 
> > > Today I'll try with a different user and if its still there I think I'll
> > > try from a live CD session.
> > > 
> > > If there are any other cache or config files I should be worrying about
> > > where these settings could be coming from please let me know!
> > > 
> > > Thanks,
> > > Luis
> > > 
> > > Heh, no, look at the later details - I think *:* got expanded on a
> > > > windows system or in wine :)  I don't believe juju did this.
> > > >
> > > > -serge
> > > >
> 
> juju will try to setup a console log when starting the container on the cli. It 
> should point to $data-dir/units/$unit-name/container.log where data-dir is 
> specified in environments.yaml, how a windows drive path got there is mystery. 

Got it.  It's done by lxc-clone.

I'll file a bug and fix it, thanks.

-serge