[lxc-users] lxc-users Digest, Vol 88, Issue 4
marcelo fortino
marcelo.fortino at gmail.com
Thu Aug 20 17:25:20 UTC 2015
Hi Tycho,
Sorry for the delay, this is the output of `lxc info --show-log documentation`
Name: documentation
Status: STOPPED
Log:
lxc 1439899131.078 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type u nsid 0 hostid
100000 range 65536
lxc 1439899131.096 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type g nsid 0 hostid
100000 range 65536
lxc 1439919572.206 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type u nsid 0 hostid
100000 range 65536
lxc 1439919572.214 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type g nsid 0 hostid
100000 range 65536
lxc 1439919572.216 WARN lxc_cgmanager -
cgmanager.c:cgm_get:993 - do_cgm_get exited with error
lxc 1439919572.217 WARN lxc_cgmanager -
cgmanager.c:cgm_get:993 - do_cgm_get exited with error
lxc 1439919675.447 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type u nsid 0 hostid
100000 range 65536
lxc 1439919675.447 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type g nsid 0 hostid
100000 range 65536
lxc 1439919675.448 DEBUG lxc_cgmanager -
cgmanager.c:cgm_dbus_connect:152 - Failed opening dbus connection:
org.freedesktop.DBus.Error.NoServer: Failed to connect to socket
/sys/fs/cgroup/cgmanager/sock: Connection refused
lxc 1439919675.448 ERROR lxc_cgmanager -
cgmanager.c:do_cgm_get:876 - Error connecting to cgroup manager
lxc 1439919675.449 WARN lxc_cgmanager -
cgmanager.c:cgm_get:993 - do_cgm_get exited with error
lxc 1439919745.987 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type u nsid 0 hostid
100000 range 65536
lxc 1439919746.015 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type g nsid 0 hostid
100000 range 65536
lxc 1439919795.561 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type u nsid 0 hostid
100000 range 65536
lxc 1439919795.561 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type g nsid 0 hostid
100000 range 65536
lxc 1439919795.563 WARN lxc_cgmanager -
cgmanager.c:cgm_get:993 - do_cgm_get exited with error
lxc 1439919795.566 WARN lxc_cgmanager -
cgmanager.c:cgm_get:993 - do_cgm_get exited with error
lxc 1439920109.667 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type u nsid 0 hostid
100000 range 65536
lxc 1439920109.667 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type g nsid 0 hostid
100000 range 65536
lxc 1439920109.694 WARN lxc_cgmanager -
cgmanager.c:cgm_get:993 - do_cgm_get exited with error
lxc 1439920109.694 INFO lxc_start -
start.c:lxc_check_inherited:224 - closed inherited fd 3
lxc 1439920109.701 INFO lxc_container -
lxccontainer.c:do_lxcapi_start:708 - Attempting to set proc title to
[lxc monitor] /var/lib/lxd/containers documentation
lxc 1439920109.701 INFO lxc_lsm -
lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor
lxc 1439920109.701 INFO lxc_seccomp -
seccomp.c:parse_config_v2:318 - processing: .reject_force_umount #
comment this to allow umount -f; not recommended.
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:410 - Adding native rule for
reject_force_umount action 0
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject
force umounts
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:413 - Adding compat rule for
reject_force_umount action 0
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject
force umounts
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:318 - processing: .[all].
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:318 - processing: .kexec_load errno 1.
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:410 - Adding native rule for kexec_load
action 327681
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:413 - Adding compat rule for kexec_load
action 327681
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:318 - processing: .open_by_handle_at errno
1.
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:410 - Adding native rule for
open_by_handle_at action 327681
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:413 - Adding compat rule for
open_by_handle_at action 327681
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:318 - processing: .init_module errno 1.
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:410 - Adding native rule for init_module
action 327681
lxc 1439920109.702 INFO lxc_seccomp -
seccomp.c:parse_config_v2:413 - Adding compat rule for init_module
action 327681
lxc 1439928842.344 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type u nsid 0 hostid
100000 range 65536
lxc 1439928842.374 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type g nsid 0 hostid
100000 range 65536
lxc 1439931895.964 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type u nsid 0 hostid
100000 range 65536
lxc 1439931895.964 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type g nsid 0 hostid
100000 range 65536
lxc 1439931895.966 DEBUG lxc_cgmanager -
cgmanager.c:cgm_dbus_connect:152 - Failed opening dbus connection:
org.freedesktop.DBus.Error.NoServer: Failed to connect to socket
/sys/fs/cgroup/cgmanager/sock: Connection refused
lxc 1439931895.966 ERROR lxc_cgmanager -
cgmanager.c:do_cgm_get:876 - Error connecting to cgroup manager
lxc 1439931895.967 WARN lxc_cgmanager -
cgmanager.c:cgm_get:993 - do_cgm_get exited with error
lxc 1440090322.129 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type u nsid 0 hostid
100000 range 65536
lxc 1440090322.149 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type g nsid 0 hostid
100000 range 65536
lxc 1440091035.586 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type u nsid 0 hostid
100000 range 65536
lxc 1440091035.586 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type g nsid 0 hostid
100000 range 65536
lxc 1440091035.587 WARN lxc_cgmanager -
cgmanager.c:cgm_get:993 - do_cgm_get exited with error
lxc 1440091035.589 WARN lxc_cgmanager -
cgmanager.c:cgm_get:993 - do_cgm_get exited with error
lxc 1440091054.353 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type u nsid 0 hostid
100000 range 65536
lxc 1440091054.353 INFO lxc_confile -
confile.c:config_idmap:1433 - read uid map: type g nsid 0 hostid
100000 range 65536
lxc 1440091054.355 WARN lxc_cgmanager -
cgmanager.c:cgm_get:993 - do_cgm_get exited with error
lxc 1440091054.357 WARN lxc_cgmanager -
cgmanager.c:cgm_get:993 - do_cgm_get exited with error
Any help appreciated
Thanks
Marcelo
---------- Mensaje reenviado ----------
From: Tycho Andersen <tycho.andersen at canonical.com>
To: LXC users mailing-list <lxc-users at lists.linuxcontainers.org>
Cc:
Date: Tue, 18 Aug 2015 15:59:18 -0700
Subject: Re: [lxc-users] error Error calling 'lxd forkstart
documentation /var/lib/lxd/containers
Hi Marcelo,
On Tue, Aug 18, 2015 at 03:30:04PM -0300, marcelo fortino wrote:
> This morning I did an apt-get update and lxd packages were upgraded.
> since then I can't start any of the container, I had this error:
>
> Error calling 'lxd forkstart documentation /var/lib/lxd/containers.
>
> The lxd.log show this:
> t=2015-08-12T14:10:59-0300 lvl=info msg="LXD is starting."
> t=2015-08-12T14:10:59-0300 lvl=info msg="Default uid/gid map:"
> t=2015-08-12T14:10:59-0300 lvl=info msg=" - u 0 100000 65536"
> t=2015-08-12T14:10:59-0300 lvl=info msg=" - g 0 100000 65536"
> t=2015-08-12T14:11:00-0300 lvl=info msg=Init driver=storage/dir
> t=2015-08-12T14:11:02-0300 lvl=info msg="looking for existing
> certificates:" cert=/var/lib/lxd/server.crt
> key=/var/lib/lxd/server.key
> t=2015-08-12T14:11:03-0300 lvl=info msg=Init driver=storage/dir
> t=2015-08-12T14:11:03-0300 lvl=info msg="LXD isn't socket activated."
> t=2015-08-12T14:11:03-0300 lvl=info msg=" - binding socket"
> socket=/var/lib/lxd/unix.socket
> t=2015-08-12T18:15:27-0300 lvl=info msg="Received 'power failure
> signal', shutting down containers."
>
>
> Lxd version 0.15 on Ubuntu 14.04. Any help to fix this?
What's the output of `lxc info --show-log documentation`?
Tycho
2015-08-18 21:35 GMT-03:00 <lxc-users-request at lists.linuxcontainers.org>:
> Send lxc-users mailing list submissions to
> lxc-users at lists.linuxcontainers.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.linuxcontainers.org/listinfo/lxc-users
> or, via email, send a message with subject or body 'help' to
> lxc-users-request at lists.linuxcontainers.org
>
> You can reach the person managing the list at
> lxc-users-owner at lists.linuxcontainers.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lxc-users digest..."
>
> Today's Topics:
>
> 1. Re: Mount directory with space in the path (Valerio Mariani)
> 2. Re: LXC and Unprivileged containers - purpose and status -
> talks (Benoit GEORGELIN - Association Web4all)
> 3. Re: Mount directory with space in the path (Tycho Andersen)
> 4. error Error calling 'lxd forkstart documentation
> /var/lib/lxd/containers (marcelo fortino)
> 5. Re: error Error calling 'lxd forkstart documentation
> /var/lib/lxd/containers (Tycho Andersen)
> 6. Communication btw container & host (SIVA SUBRAMANIAN.P)
> 7. Re: Communication btw container & host (Andrey Repin)
>
>
> ---------- Mensaje reenviado ----------
> From: Valerio Mariani <valerio.mariani at gmx.de>
> To: LXC users mailing-list <lxc-users at lists.linuxcontainers.org>
> Cc:
> Date: Tue, 18 Aug 2015 14:18:05 +0200
> Subject: Re: [lxc-users] Mount directory with space in the path
> Dear Andrey,
>
> thanks for your answer. So, I did this (psana is the software I am
> working on):
>
> lxc config device add centos6-amd64-psana opt-working disk
> source="/data/Data/Psana Tests/" path=/opt/working
>
> Then if I try:
>
> lxc config device show centos6-amd64-psana
>
> I see:
>
> ...
> opt-working
> source: /data/Data/Psana Tests/
> type: disk
> path: /opt/working
> ...
>
> However, when I start the container:
>
> lxc start centos6-amd64-psana
> error Error calling 'lxd forkstart centos6-amd64-psana
> /var/lib/lxd/containers /var/log/lxd/centos6-amd64-psana/lxc.conf':
> err='exit status 1'
>
> The log says:
>
> lxc 1439899856.718 ERROR lxc_conf -
> conf.c:mount_entry:1720 - No such file or directory - failed to mount
> '/data/Data/Psana' on '/usr/lib/x86_64-linux-gnu/lxc/Tests/'
> lxc 1439899856.718 ERROR lxc_conf - conf.c:lxc_setup:3801
> - failed to setup the mount entries for 'centos6-amd64-psana'
>
> So, when it tries to mount the directory, it cuts the path at the first
> space... then takes the second part of the string as the target path for
> the mount.
>
> Should I report this as a bug on the gitHub page?
>
> Thank you for your help
>
> Valerio
>
>
>
>
>
>
>
>
>
>
> On 17.08.2015 18:41, Andrey Repin wrote:
>> Greetings, Valerio Mariani!
>>
>>> I have been using this syntax to mount some of the hosts's directories in the container:
>>> lxc config device add gp sources disk source=$HOME/p/gratipay.com path=/opt/srv
>> lxc config device add gp sources disk source="$HOME/p/gratipay.com" path=/opt/srv
>> ?
>>
>>> However, I don't see to be able to use a host path (source=) with a
>>> space in it. I tried using forward slash (\), single quotes ('),
>>> double quotes (") around the path, everything, but it gets put in the
>>> configuration with the path truncated at the first space.... Is it
>>> possible to use paths with spaces in it?
>>
>
>
>
>
> ---------- Mensaje reenviado ----------
> From: Benoit GEORGELIN - Association Web4all <benoit.georgelin at web4all.fr>
> To: lxc-users <lxc-users at lists.linuxcontainers.org>
> Cc:
> Date: Tue, 18 Aug 2015 16:21:18 +0200 (CEST)
> Subject: Re: [lxc-users] LXC and Unprivileged containers - purpose and status - talks
> Thanks for your answer.
> Looks like there is good ressources .
>
> Cordialement,
>
> Benoît Georgelin
>
> ________________________________
> De: "Luis M. Ibarra" <michael.ibarra at gmail.com>
> À: "lxc-users" <lxc-users at lists.linuxcontainers.org>
> Envoyé: Lundi 17 Août 2015 12:41:43
> Objet: Re: [lxc-users] LXC and Unprivileged containers - purpose and status - talks
>
> Hi all,
>
> There's going to be excellent talks in ContainerCon[1] this week, but I don't know if the talks are going to be streamed later.
>
> For User Namespaces, I follow this tutorial[2] which explains pretty well how user namespaces work. Also, check user_namespaces(7) and capabilities(7), here you find pretty much how linux capabilities is used in conjunction with user namespaces to get super user inside the container regarding being created as a normal user in the host.
> Finally, in lxd/specs/userns-idmap[3] you'll find many cases where user namespaces can save your life if things go really wrong.
>
> If you want a simple solution of unpriv containers, you should check LXD which is really awesome, but it's still in heavy development.
>
>
> [1] http://events.linuxfoundation.org/events/containercon/program/schedule
> [2] https://www.youtube.com/watch?v=kKCdPouT-dQ
> [3] https://github.com/lxc/lxd/blob/master/specs/userns-idmap.md
>
>
>
> Greetings,
>
>
>
>
> 2015-08-17 3:17 GMT-05:00 Narcis Garcia <informatica at actiu.net>:
>>
>> I've read somewhere:
>> "Ubuntu is also one of the few (if not only) Linux distributions to come
>> by default with everything that's needed for safe, unprivileged LXC
>> containers" - and not LTS versions.
>>
>>
>> El 17/08/15 a les 06:48, Benoit GEORGELIN - Association Web4all ha escrit:
>> > Hi lxc-users :)
>> >
>> > I'm currently working and playing around with LXC containers. I came
>> > across "Unprivileged Containers"
>> > I would like to get some feedback about this really interesting feature.
>> > It's not easy to get a good tour about the technology and about the
>> > maturity of this kind of containers. First because I'm not technical
>> > enough to understand the differences between LXC and OpenVZ (besides
>> > Cgroups and kernels needs) , second because I'm not able to find
>> > documentation, talks or paper about it.
>> > I'm here to talk about it, try to merge information from you guys and
>> > eventually make something public that can be shared to everyone having
>> > the same questions :)
>> >
>> > As I'm looking at containers for shared environments, I'm more concerned
>> > about security. There is few concerns I have regarding LXC with both
>> > privileged and unprivileged containers.
>> >
>> > -Network stand point
>> >
>> > By default LXC have great network management and integration (with
>> > privileged containers) but this is without any secure solution about
>> > network spoofing (MAC, IP, Etc..)
>> > I know, maybe it's not LXC's business to manage network like that, but
>> > looking how good is the project seems to be, I'm really surprised there
>> > is not any solutions that comes with LXC to integrate those kind of
>> > (basics) security.
>> >
>> > One container=>One MAC address=> One or more specifics IP address.
>> >
>> > Even if the goal of linuxcontainers is to be "vendor neutral" I think
>> > there something missing here to be more "user friendly" and "out of the
>> > box" . I think most of LXC user will have more than one containers to
>> > deploy and it may be the best to provide easy integrated solution
>> > regarding this specific
>> > aspect of networking.
>> >
>> > I Have been using OpenVswitch (Open Flow) to add such security but from
>> > what I can tell, this is not documented and self learning on those
>> > technology take a long time. You can see the archive here
>> > : https://www.mail-archive.com/lxc-users@lists.linuxcontainers.org/msg03609.html
>> >
>> > (?) What should the position be when you need to deploy lots of LXC
>> > containers and give root access to the container ?
>> > The question doesn't happen with unprivileged containers, looks like
>> > there is no way to change network info, but this is not the solution if
>> > you wanna run privileged containers and stay safe.
>> >
>> > - System security stand point
>> >
>> > Dmesg
>> > As a simple and quick test, dmesg information of the HOST are in the
>> > unprivileged container.
>> > (?) Maybe there is a technical limit about that ?
>> >
>> > (?) What can be the best way to understand more how build are
>> > unprivileged container and what can be done to help . Is this only about
>> > Cgroups? Apparmor ? both?
>> > Maybe have more information about the interaction between security parts
>> > will be a nice to have :)
>> >
>> >
>> > - Maturity of the solution with unprivileged containers.
>> > I know there is a lot of things going on with this kind of containers. I
>> > would like to know more about the perspective and the goal .
>> >
>> > (?) what unprivileged containers are made for ?
>> > (?) Is this only to prevent security issues from any process running out
>> > of an LXC (privileged) container ?
>> > Or is it more to give the opportunity to no-root user to execute
>> > LXC containers ?
>> >
>> > (?) Let's say it's for security purpose only in case of a process
>> > running out of a container, how big is the possibility that happen ?
>> > from one to ten ?
>> >
>> > Story of my first experience with unprivileged container :
>> >
>> > I'm running debian jessie to try my first unprivileged container.
>> > lxc-create -n debian8 -t downlowd -- -d debian -r jessie -a amd64
>> >
>> > First thing I wanna do, install sshd daemon . No problem.
>> > Second thing, starting sshd after install : service sshd restart .
>> > Result: [sshd] <defunct>
>> > Looks like there is something weird...
>> > service sshd start : Result : Process running
>> > But wait, not able to connect . :/
>> > I had to : sed -ri 's/^session\s+required\s+pam_loginuid.so$/session
>> > optional pam_loginuid.so/' /etc/pam.d/sshd
>> >
>> > (?) Now I can connect but "pam_loginuid" cannot be used at all ?
>> >
>> > Then , what can I see, every SSHD connection failure show a new sshd
>> > <defunct> process
>> >
>> > ps auxf|grep sshd|grep defunct|wc -l
>> > 503
>> >
>> > (?) any idea or know problem ? Is something on my configuration ?
>> >
>> > It happen with others process like :
>> > [chef-client] <defunct>
>> > [bash] <defunct>
>> > [sshd] <defunct>
>> >
>> > I just wanna understand if those issue are definitively a miss
>> > configuration on my side or that can be easily explained ? :(
>> >
>> > - init.d with unprivileged
>> > (?) Maybe because I have a lack of knowledge in this area, but why
>> > there is nothing starting up automatically from a unprivileged container ?
>> > (?) What can be used as a workaround ?
>> >
>> >
>> > Well, beside those points, I can get an unprivileged container running
>> > httpd, php5, mysql :)
>> > Pretty quick and easy . Templates are a very good thing to use . (thx)
>> >
>> > Now I'm looking forward to read your experience and share some technical
>> > or unprivileged containers story !
>> >
>> > Cheers,
>> >
>> >
>> > Cordialement,
>> >
>> > Benoît Georgelin
>> > Afin de contribuer au respect de l'environnement, merci de n'imprimer ce
>> > mail qu'en cas de nécessité
>> >
>> >
>> >
>> > _______________________________________________
>> > lxc-users mailing list
>> > lxc-users at lists.linuxcontainers.org
>> > http://lists.linuxcontainers.org/listinfo/lxc-users
>> >
>> _______________________________________________
>> lxc-users mailing list
>> lxc-users at lists.linuxcontainers.org
>> http://lists.linuxcontainers.org/listinfo/lxc-users
>
>
>
>
> --
> Luis M. Ibarra
>
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
>
> ---------- Mensaje reenviado ----------
> From: Tycho Andersen <tycho.andersen at canonical.com>
> To: LXC users mailing-list <lxc-users at lists.linuxcontainers.org>
> Cc:
> Date: Tue, 18 Aug 2015 09:07:49 -0700
> Subject: Re: [lxc-users] Mount directory with space in the path
> On Tue, Aug 18, 2015 at 02:18:05PM +0200, Valerio Mariani wrote:
>> Dear Andrey,
>>
>> thanks for your answer. So, I did this (psana is the software I am
>> working on):
>>
>> lxc config device add centos6-amd64-psana opt-working disk
>> source="/data/Data/Psana Tests/" path=/opt/working
>>
>> Then if I try:
>>
>> lxc config device show centos6-amd64-psana
>>
>> I see:
>>
>> ...
>> opt-working
>> source: /data/Data/Psana Tests/
>> type: disk
>> path: /opt/working
>> ...
>>
>> However, when I start the container:
>>
>> lxc start centos6-amd64-psana
>> error Error calling 'lxd forkstart centos6-amd64-psana
>> /var/lib/lxd/containers /var/log/lxd/centos6-amd64-psana/lxc.conf':
>> err='exit status 1'
>>
>> The log says:
>>
>> lxc 1439899856.718 ERROR lxc_conf -
>> conf.c:mount_entry:1720 - No such file or directory - failed to mount
>> '/data/Data/Psana' on '/usr/lib/x86_64-linux-gnu/lxc/Tests/'
>> lxc 1439899856.718 ERROR lxc_conf - conf.c:lxc_setup:3801
>> - failed to setup the mount entries for 'centos6-amd64-psana'
>>
>> So, when it tries to mount the directory, it cuts the path at the first
>> space... then takes the second part of the string as the target path for
>> the mount.
>>
>> Should I report this as a bug on the gitHub page?
>
> Thanks, I think this is a bug in LXD, can you try:
>
> https://github.com/tych0/lxd/commit/08f4e8580c42fc38063b9dfa53dc2e6550a0ed6c
>
> and see if that fixes it?
>
> Thanks,
>
> Tycho
>
>
>
> ---------- Mensaje reenviado ----------
> From: marcelo fortino <marcelo.fortino at gmail.com>
> To: lxc-users at lists.linuxcontainers.org
> Cc:
> Date: Tue, 18 Aug 2015 15:30:04 -0300
> Subject: [lxc-users] error Error calling 'lxd forkstart documentation /var/lib/lxd/containers
> This morning I did an apt-get update and lxd packages were upgraded.
> since then I can't start any of the container, I had this error:
>
> Error calling 'lxd forkstart documentation /var/lib/lxd/containers.
>
> The lxd.log show this:
> t=2015-08-12T14:10:59-0300 lvl=info msg="LXD is starting."
> t=2015-08-12T14:10:59-0300 lvl=info msg="Default uid/gid map:"
> t=2015-08-12T14:10:59-0300 lvl=info msg=" - u 0 100000 65536"
> t=2015-08-12T14:10:59-0300 lvl=info msg=" - g 0 100000 65536"
> t=2015-08-12T14:11:00-0300 lvl=info msg=Init driver=storage/dir
> t=2015-08-12T14:11:02-0300 lvl=info msg="looking for existing
> certificates:" cert=/var/lib/lxd/server.crt
> key=/var/lib/lxd/server.key
> t=2015-08-12T14:11:03-0300 lvl=info msg=Init driver=storage/dir
> t=2015-08-12T14:11:03-0300 lvl=info msg="LXD isn't socket activated."
> t=2015-08-12T14:11:03-0300 lvl=info msg=" - binding socket"
> socket=/var/lib/lxd/unix.socket
> t=2015-08-12T18:15:27-0300 lvl=info msg="Received 'power failure
> signal', shutting down containers."
>
>
> Lxd version 0.15 on Ubuntu 14.04. Any help to fix this?
>
> many thanks.
> Marcelo
>
>
>
> ---------- Mensaje reenviado ----------
> From: Tycho Andersen <tycho.andersen at canonical.com>
> To: LXC users mailing-list <lxc-users at lists.linuxcontainers.org>
> Cc:
> Date: Tue, 18 Aug 2015 15:59:18 -0700
> Subject: Re: [lxc-users] error Error calling 'lxd forkstart documentation /var/lib/lxd/containers
> Hi Marcelo,
>
> On Tue, Aug 18, 2015 at 03:30:04PM -0300, marcelo fortino wrote:
>> This morning I did an apt-get update and lxd packages were upgraded.
>> since then I can't start any of the container, I had this error:
>>
>> Error calling 'lxd forkstart documentation /var/lib/lxd/containers.
>>
>> The lxd.log show this:
>> t=2015-08-12T14:10:59-0300 lvl=info msg="LXD is starting."
>> t=2015-08-12T14:10:59-0300 lvl=info msg="Default uid/gid map:"
>> t=2015-08-12T14:10:59-0300 lvl=info msg=" - u 0 100000 65536"
>> t=2015-08-12T14:10:59-0300 lvl=info msg=" - g 0 100000 65536"
>> t=2015-08-12T14:11:00-0300 lvl=info msg=Init driver=storage/dir
>> t=2015-08-12T14:11:02-0300 lvl=info msg="looking for existing
>> certificates:" cert=/var/lib/lxd/server.crt
>> key=/var/lib/lxd/server.key
>> t=2015-08-12T14:11:03-0300 lvl=info msg=Init driver=storage/dir
>> t=2015-08-12T14:11:03-0300 lvl=info msg="LXD isn't socket activated."
>> t=2015-08-12T14:11:03-0300 lvl=info msg=" - binding socket"
>> socket=/var/lib/lxd/unix.socket
>> t=2015-08-12T18:15:27-0300 lvl=info msg="Received 'power failure
>> signal', shutting down containers."
>>
>>
>> Lxd version 0.15 on Ubuntu 14.04. Any help to fix this?
>
> What's the output of `lxc info --show-log documentation`?
>
> Tycho
>
>
>
> ---------- Mensaje reenviado ----------
> From: "SIVA SUBRAMANIAN.P" <psiva87 at gmail.com>
> To: LXC users mailing-list <lxc-users at lists.linuxcontainers.org>
> Cc:
> Date: Tue, 18 Aug 2015 16:35:38 -0700
> Subject: [lxc-users] Communication btw container & host
> Hi,
> Can some one throw light on the communication option available between the host and container. I'm planning to run main application in container and all its dependencies outside it.
>
> Regards,
> Sivasubramanian
>
>
> ---------- Mensaje reenviado ----------
> From: Andrey Repin <anrdaemon at yandex.ru>
> To: "SIVA SUBRAMANIAN.P" <lxc-users at lists.linuxcontainers.org>
> Cc:
> Date: Wed, 19 Aug 2015 03:28:05 +0300
> Subject: Re: [lxc-users] Communication btw container & host
> Greetings, SIVA SUBRAMANIAN.P!
>
>> Can some one throw light on the communication option available between the
>> host and container. I'm planning to run main application in container and all its dependencies outside it.
>
> Define "dependencies"?
> Without knowing, what exactly you want to do, there's no way to tell you, how
> you can achieve your desired result.
>
>
> --
> With best regards,
> Andrey Repin
> Wednesday, August 19, 2015 03:27:26
>
> Sorry for my terrible english...
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
More information about the lxc-users
mailing list