if lxc config is modified to autostart containers, those containers that are
specified in /etc/lxc/auto will be auto started.
This is from https://help.ubuntu.com/lts/serverguide/lxc.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
this bug is resolved in juju-core fwiw.
On Fri, Dec 13, 2013 at 2:28 PM, Dimitri John Ledkov launch...@surgut.co.uk
wrote:
if lxc config is modified to autostart containers, those containers that
are specified in /etc/lxc/auto will be auto started.
This is from
** Changed in: juju
Importance: Medium = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/955576
Title:
'local:' services not started on reboot
To manage notifications about
** Changed in: juju
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/955576
Title:
'local:' services not started on reboot
To manage notifications
** Changed in: juju
Milestone: None = 0.8
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/955576
Title:
'local:' services not started on reboot
To manage notifications about this
I'm putting a production tag on this to put it on our things that
prevent Juju being used in production environments; developers can't
push to prod if we keep resetting their environments.
** Tags added: production
--
You received this bug notification because you are a member of Ubuntu
Server
Any news on this? I think that Juju on LXC shouldn't be treated as a
second class citizen, it could perfectly solve someone (mine :) needs!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
** Changed in: juju
Milestone: 0.6 = None
** Changed in: juju (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/955576
Title:
'local:'
** Changed in: juju
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/955576
Title:
'local:' services not started on reboot
To manage notifications about
** Changed in: juju
Milestone: galapagos = honolulu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/955576
Title:
'local:' services not started on reboot
To manage notifications
** Changed in: juju
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/955576
Title:
'local:' services not started on reboot
To manage notifications
** Changed in: juju
Milestone: None = galapagos
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/955576
Title:
'local:' services not started on reboot
To manage notifications about
This is documented as a limitation here:
https://juju.ubuntu.com/docs/provider-configuration-local.html
However I agree that it would be nice if the local environment could be
recovered after a host restart.
** Changed in: juju (Ubuntu)
Status: New = Confirmed
** Changed in: juju
Just a note: the local storage-server and machine-agent are now
upstartified; the missing pieces are zookeeper and the lxc containers,
neither of which should be tricky to fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in
William, thanks that is great news.
James, to call this a limitation is IMHO a major understatement. Since
all services, units, etc are removed after a destroy-environment, the
local environment is nothing more than for testing or demonstration
purposes. Of course, it states right in the page you
15 matches
Mail list logo
