hello
I use debian testing 7.0
kernel: Linux Miaou 3.2.0-2-686-pae #1 SMP Mon Jun 11 18:27:04 UTC 2012 i686
GNU/Linux
lxc version: 0.8.0~rc1-4
lxctl version 0.3.1+debian-1
I create news linux container with lxc-create -n err404-2 -t debian
all seems work well with lxc-start -n err404-2, nothing
Hello,
yesterday we did some testing of LXC on wheezy as well and got the
same results.
Seems like the necessary device nodes aren't created (/dev/tty*)
and /etc/inittab needs to be modified.
Example:
c1:2345:respawn:/sbin/getty 38400 tty1 linux
We also found other bugs and needed
Thanks for looking into it.
It means some applications cannot run unmodified in a container then?
/Hans
On 07/02/12 19:08, Serge Hallyn wrote:
This appears to be a cgroup issue (presumably by design). Without involving
lxc, just do
sudo bash
# mkdir /sys/fs/cgroup/cpu/1
# echo $$
On 07/03/2012 02:29 PM, Hans Feldt wrote:
Thanks for looking into it.
It means some applications cannot run unmodified in a container then?
Did you try by mounting the cgroup but without the 'cpu' subsystem ?
-- Daniel
/Hans
On 07/02/12 19:08, Serge Hallyn wrote:
This appears to be a
On 28 June 2012 23:11, Serge Hallyn serge.hal...@canonical.com wrote:
Quoting Ben Butler-Cole (b...@bridesmere.com):
However the default dnsmasq configuration, combined with the way EC2's
DNS
servers behave, means that my containers are getting EC2-like DNS names
assigned automatically
On Tue, Jul 3, 2012 at 7:13 PM, Stefan Schlesinger s...@ono.at wrote:
Hello,
yesterday we did some testing of LXC on wheezy as well and got the
same results.
Seems like the necessary device nodes aren't created (/dev/tty*)
and /etc/inittab needs to be modified.
Example:
