[Lxc-users] Problem with: lxc.autodev=1
Frederic Crozat
fcrozat at suse.com
Mon Apr 22 08:25:34 UTC 2013
Le samedi 20 avril 2013 à 15:33 -0400, Michael H. Warfield a écrit :
> On Sat, 2013-04-20 at 21:13 +0200, Andreas Otto wrote:
> > Hi all,
>
> > my problem: the "autodev" create devices with wrong permissions:
>
> > > ls -ald /dev/*
> > crw-rw---- 1 root tty 136, 16 Apr 20 18:34 /dev/console
> > lrwxrwxrwx 1 root root 11 Apr 20 18:34 /dev/core -> /proc/kcore
> > lrwxrwxrwx 1 root root 13 Apr 20 18:34 /dev/fd -> /proc/self/fd
> > crwxr-xr-x 1 root root 1, 7 Apr 20 18:34 /dev/full
> > drwxr-xr-x 2 root root 0 Apr 20 18:34 /dev/hugepages
> > prw------- 1 root root 0 Apr 20 18:34 /dev/initctl
> > lrwxrwxrwx 1 root root 7 Apr 20 18:34 /dev/kmsg -> console
> > srw-rw-rw- 1 root root 0 Apr 20 18:34 /dev/log
> > drwxrwxrwt 2 root root 40 Apr 20 18:34 /dev/mqueue
> > crwxr-xr-x 1 root root 1, 3 Apr 20 18:34 /dev/null
> > lrwxrwxrwx 1 root root 13 Apr 20 18:34 /dev/ptmx -> /dev/pts/ptmx
> > drwxr-xr-x 2 root root 0 Apr 20 18:34 /dev/pts
> > crwxr-xr-x 1 root root 1, 8 Apr 20 18:34 /dev/random
> > drwxrwxrwt 2 root root 40 Apr 20 18:34 /dev/shm
> > lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stderr -> /proc/self/fd/2
> > lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stdin -> /proc/self/fd/0
> > lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stdout -> /proc/self/fd/1
> > crwxr-xr-x 1 root root 5, 0 Apr 20 18:34 /dev/tty
> > crw-rw---- 1 root tty 136, 12 Apr 20 18:34 /dev/tty1
> > crw-rw---- 1 root tty 136, 13 Apr 20 18:34 /dev/tty2
> > crw-rw---- 1 root tty 136, 14 Apr 20 18:34 /dev/tty3
> > crw-rw---- 1 root tty 136, 15 Apr 20 18:34 /dev/tty4
> > crwxr-xr-x 1 root root 1, 9 Apr 20 18:34 /dev/urandom
> > crwxr-xr-x 1 root root 1, 5 Apr 20 18:34 /dev/zero
>
> > check the permissions for "/dev/tty" or "/dev/null" as example.
>
> I've seen this before when I set autodev=1 on a container which was NOT
> running systemd for init. Reviewing the code and all, it looked like it
> should be setting the correct permissions and yet it came out wrong for
> several devices. In my case, I finally got my Fedora 17 containers
> working fine (autodev=1 w/ systemd) and my Fedora 14 containers right
> with autodev=0 w/o systemd. If I turned autodev=1 on the Fedora 14
> containers, it did what you're describing. That was back when we were
> first working on the systemd support. I don't recall testing that
> condition after we cut the patches loose for 0.9.0 that included systemd
> support in both the containers and the host.
Expect I did the backport of autodev in lxc 0.8.0 package we ship in
12.3, so we could support 12.3 guest nicely.
> 1) Is OpenSuse 12.3 running systemd init (I don't run OpenSuse and,
> unfortunately, the lxc-opensuse template doesn't seem to work for me on
> Fedora)?
Yes, we only support systemd starting with 12.3
--
Frederic Crozat <fcrozat at suse.com>
SUSE
More information about the lxc-users
mailing list