The short answer is, if login prompt is going to the system console then
that means /dev/console was recreated in the container as 5:1.
What you probably want to do is grab the lxc version from
git://github.com/lxc/lxc.git#staging and set lxc.autodev=1 in your
container config. Then systemd in
On Thu, 2012-12-06 at 11:35 +, Benoit Lourdelet wrote:
Hello,
On fedora 18 Linux localhost.localdomain 3.6.7-5.fc18.x86_64 #1 SMP Tue
Nov 20 19:40:08 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
LXC version 0.8.0
This is currently a known problem with running systemd in a container.
I haven't
Quoting John (l...@jelmail.com):
On 05/12/12 21:59, Serge Hallyn wrote:
You have to specify a template, i.e. '-t debian'.
Oh. I wasn't using a template.
Up to now, I have an existing root fileyststem, say
/srv/lxc/mycontainer.x86_64 that is pointed to by my configuration
file, say
On 06/12/12 17:10, Serge Hallyn wrote:
Quoting John (l...@jelmail.com):
On 05/12/12 21:59, Serge Hallyn wrote:
You have to specify a template, i.e. '-t debian'.
Oh. I wasn't using a template.
Up to now, I have an existing root fileyststem, say
/srv/lxc/mycontainer.x86_64 that is pointed to
On 12/06/2012 02:45 PM, John wrote:
On 06/12/12 17:10, Serge Hallyn wrote:
Quoting John (l...@jelmail.com):
On 05/12/12 21:59, Serge Hallyn wrote:
You have to specify a template, i.e. '-t debian'.
Oh. I wasn't using a template.
Up to now, I have an existing root fileyststem, say
On 06/12/12 19:48, Stéphane Graber wrote:
On 12/06/2012 02:45 PM, John wrote:
On 06/12/12 17:10, Serge Hallyn wrote:
Quoting John (l...@jelmail.com):
On 05/12/12 21:59, Serge Hallyn wrote:
You have to specify a template, i.e. '-t debian'.
Oh. I wasn't using a template.
Up to now, I have
On Thu, Dec 6, 2012 at 12:00 PM, John l...@jelmail.com wrote:
While on the subject, any reason for lxc-destroy now being destructive?
Wait, isn't that the point? It's in the name and all.
When was it ever nondestructive?
On 06/12/12 20:06, Dan Kegel wrote:
On Thu, Dec 6, 2012 at 12:00 PM, John l...@jelmail.com wrote:
While on the subject, any reason for lxc-destroy now being destructive?
Wait, isn't that the point? It's in the name and all.
When was it ever nondestructive?
It only destroyed the
Quoting John (l...@jelmail.com):
On 06/12/12 20:06, Dan Kegel wrote:
On Thu, Dec 6, 2012 at 12:00 PM, John l...@jelmail.com wrote:
While on the subject, any reason for lxc-destroy now being destructive?
Wait, isn't that the point? It's in the name and all.
When was it ever
