Quoting Marc Paradise ([email protected]):
> On Fri, Oct 25, 2013 at 10:30 AM, Serge Hallyn <[email protected]>wrote:
> >
> >
> > Can you please do an lxc-start with '-l info -o outfile' options and
> > attach the outfile? Also show the /proc/self/mounts and
> > /proc/self/mountinfo contents from both the host and the container.
> >
>
> I've attached mountinfo and mounts from the host, but I can't reach the
> guest via console or ssh to grab the same there.
You don't need to. You can ps -ef to find an /sbin/init that is not pid
1, and do /proc/$pid/mount{s,info} for that pid.
The main thing I notice in your logs is that
21 15 0:16 / /sys/fs/cgroup rw,relatime - cgroup cgroup
rw,hugetlb,perf_event,blkio,freezer,devices,memory,cpuacct,cpu,cpuset
...
33 21 0:26 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime - cgroup
systemd rw,name=systemd
These are weird. Normally we have all cgroups mounted separately in
subdirs of /sys/fs/cgroup. I.e. freezer on /sys/fs/cgroup/freezer,
cpuset on /sys/fs/cgroup/cpuset, etc. You don't have cgroup-lite
package installed? What is mounting /sys/fs/cgroup? Is it done by
/etc/fstab?
Secondly, since /sys/fs/cgroup is a cgroupfs, it is not ok to
create a directory under that and mount systemd cgroup system over
it. /sys/fs/cgroup/systemd, once created, represents a cgroup called
systemd, which tasks can be inserted into. If you now, for instance,
create a container called 'systemd' you'll be in a world of hurt.
-serge
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Lxc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxc-users
