Quoting Tamas Papp (tom...@martos.bme.hu):
On 10/04/2013 04:11 PM, Tamas Papp wrote:
hi,
Starting a container from cli by lxc-start works fine, lxc-info shows the
right state.
Using upstart:
start lxc-instance NAME=archiva-test CONFIG=/tank/lxc/archiva-test/config
#
On 10/07/2013 07:09 PM, Serge Hallyn wrote:
An easy way to reproduce this without zfs is:
sudo lxc-create -t ubuntu -n r0
sudo cp /var/lib/lxc/r0/config /tmp
sudo lxc-start -n r0 -f /tmp/config -d
sudo lxc-info -n r0
(it shows up as stopped)
sudo
Quoting Tamas Papp (tom...@martos.bme.hu):
On 10/07/2013 07:09 PM, Serge Hallyn wrote:
An easy way to reproduce this without zfs is:
sudo lxc-create -t ubuntu -n r0
sudo cp /var/lib/lxc/r0/config /tmp
sudo lxc-start -n r0 -f /tmp/config -d
sudo lxc-info -n r0
On 10/04/2013 04:11 PM, Tamas Papp wrote:
hi,
Starting a container from cli by lxc-start works fine, lxc-info shows the
right state.
Using upstart:
start lxc-instance NAME=archiva-test CONFIG=/tank/lxc/archiva-test/config
# lxc-info -n archiva-test
state: STOPPED
Though the
hi,
Starting a container from cli by lxc-start works fine, lxc-info shows the right
state.
Using upstart:
start lxc-instance NAME=archiva-test CONFIG=/tank/lxc/archiva-test/config
# lxc-info -n archiva-test
state: STOPPED
Though the container gets started.
As a result I cannot use
On 13/10/04 10:29, Stéphane Graber wrote:
On Fri, Oct 04, 2013 at 04:11:58PM +0200, Tamas Papp wrote:
hi,
Starting a container from cli by lxc-start works fine, lxc-info shows the
right state.
Using upstart:
start lxc-instance NAME=archiva-test
On 10/04/2013 05:05 PM, zoolook wrote:
I have also seen this problem from time to time in different boxes and
different
versions of lxc. It's not easily reproducible and I can't remember if I
reported
it (maybe not since I couldn't make a 100% reproducible test case).
I also use a
