Quoting Tim Penhey (tim.pen...@canonical.com): > On 19/05/15 05:34, Serge Hallyn wrote: > > Quoting Tim Penhey (tim.pen...@canonical.com): > >> $ apt-cache policy lxd > >> lxd: > >> Installed: 0.9-0ubuntu2~ubuntu14.04.1~ppa1 > >> Candidate: 0.9-0ubuntu2~ubuntu14.04.1~ppa1 > >> Version table: > >> *** 0.9-0ubuntu2~ubuntu14.04.1~ppa1 0 > >> 500 http://ppa.launchpad.net/ubuntu-lxc/lxd-git-master/ubuntu/ > >> trusty/main amd64 Packages > >> 100 /var/lib/dpkg/status > >> > >> However, the container would have been created just over a week ago, so > >> the release before Tuesday. > >> > >> > >> On 15/05/15 16:54, Tycho Andersen wrote: > >>> lxc info trusty-lxd-test --show-log > >> > >> $ lxc info trusty-lxd-test --show-log > >> Name: trusty-lxd-test > >> Status: STOPPED > >> > >> Log: > >> > >> lxc_container 1431054105.261 ERROR lxc_confile - > >> confile.c:config_mount_auto:1413 - Invalid filesystem to automount: > >> sys:mixed > >> lxc_container 1431054105.261 ERROR lxc_parse - > >> parse.c:lxc_file_for_each_line:57 - Failed to parse config: > >> lxc.mount.auto = cgroup:mixed proc:mixed sys:mixed > >> > >> lxc_container 1431054105.261 ERROR lxc_parse - > >> parse.c:lxc_file_for_each_line:57 - Failed to parse config: lxc.include > >> = /usr/share/lxc/config/common.conf > > > > Not sure whether this was your mailer line-wrapping - can you > > confirm that the \n before the = was there in the logs? > > Yes, just mailer line wrapping. > > All the log messages are on their own line, however there is a blank > line after each 'ERROR lxc_parse' line.
That's too bad, because all of these seem valid. To be sure, what is your installed lxc version? _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
