<p dir="ltr">1. It is running with --disable -seccomp option.<br>
2. My target is not havving implementation of syscall no 254(set_thread_area ()) and 255(get_thread_area ()).<br>
3. I tried to run lxc with CLONE_SETTLS option but is ia crshing may be due to non existence of syscall 254 and 255.</p>
<p dir="ltr">Vivek</p>
<div class="gmail_quote">On Jan 3, 2014 5:30 PM, <<a href="mailto:lxc-users-request@lists.linuxcontainers.org">lxc-users-request@lists.linuxcontainers.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Send lxc-users mailing list submissions to<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:lxc-users-request@lists.linuxcontainers.org">lxc-users-request@lists.linuxcontainers.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:lxc-users-owner@lists.linuxcontainers.org">lxc-users-owner@lists.linuxcontainers.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of lxc-users digest..."<br>
<br>Today's Topics:<br>
<br>
1. Re: Cannot set up thread local storage: unknown error<br>
(Serge Hallyn)<br>
2. lxc-start hangs with no output (Piotr Isajew)<br>
3. Cannot stop busybox container (Kevin Wilson)<br>
4. Re: lxc-start hangs with no output (Giuseppe Tofoni)<br>
5. Re: lxc-start hangs with no output (Piotr Isajew)<br>
<br><br>---------- Forwarded message ----------<br>From: Serge Hallyn <<a href="mailto:serge.hallyn@ubuntu.com">serge.hallyn@ubuntu.com</a>><br>To: LXC users mailing-list <<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a>><br>
Cc: <br>Date: Thu, 2 Jan 2014 09:34:22 -0600<br>Subject: Re: [lxc-users] Cannot set up thread local storage: unknown error<br>Quoting Vivek Singh (<a href="mailto:vivek.siwan@gmail.com">vivek.siwan@gmail.com</a>):<br>
> Hello,<br>
> I am very new to lxc container. When I am trying to run it with libseccomp<br>
> on my arm target it produces following error with command.<br>
> "Lxc-execute -n name ls"<br>
> "Cannot set up thread-local storage unknown error".<br>
><br>
> Please provide your suggestions to me so that I can proceed forward.<br>
<br>
Confirm that it doesn't work with seccomp disabled. Run lxc-execute<br>
with '-l info -o outout' and look for information in outout as well<br>
as in syslog.<br>
<br>
Looking at arch/arm/include/uapi/asm/unist.h, you might need to allow<br>
syscalls __NR_SYSCALL_BASE+253, __NR_SYSCALL_BASE+254 and<br>
__NR_SYSCALL_BASE+255.<br>
<br>
<br><br>---------- Forwarded message ----------<br>From: Piotr Isajew <<a href="mailto:pki@ex.com.pl">pki@ex.com.pl</a>><br>To: <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
Cc: <br>Date: Fri, 3 Jan 2014 09:37:15 +0100<br>Subject: [lxc-users] lxc-start hangs with no output<br>Hi,<br>
<br>
I wanted do try out lxc on Slackware 14.1 64-bit. lxc-create<br>
works without problems. I'm however unable to start a container.<br>
<br>
After I do i.e.:<br>
<br>
lxc-start -n vs0<br>
<br>
the command just hangs with no output, consuming all the CPU<br>
resources and eventually eating up all the memory.<br>
<br>
I've spent last three days trying to get it work but I think I've<br>
ran out of ideas.<br>
<br>
<br>
log file contains:<br>
<br>
lxc-start 1388667324.768 INFO lxc_start_ui - using rcfile /var/lib/lxc/vs0/config<br>
lxc-start 1388667324.769 INFO lxc_apparmor - apparmor_load - apparmor is disabled<br>
lxc-start 1388667324.770 DEBUG lxc_conf - allocated pty '/dev/pts/2' (5/6)<br>
lxc-start 1388667324.771 DEBUG lxc_conf - allocated pty '/dev/pts/3' (7/8)<br>
lxc-start 1388667324.771 DEBUG lxc_conf - allocated pty '/dev/pts/4' (9/10)<br>
lxc-start 1388667324.771 DEBUG lxc_conf - allocated pty '/dev/pts/5' (11/12)<br>
lxc-start 1388667324.771 INFO lxc_conf - tty's configured<br>
lxc-start 1388667324.771 DEBUG lxc_console - using '/tmp/console.log' as console log<br>
lxc-start 1388667324.771 DEBUG lxc_console - using '/dev/tty' as console<br>
lxc-start 1388667324.771 DEBUG lxc_start - sigchild handler set<br>
lxc-start 1388667324.771 INFO lxc_start - 'vs0' is initialized<br>
lxc-start 1388667324.777 DEBUG lxc_start - Not dropping cap_sys_boot or watching utmp<br>
<br>
lxc-start 1388667324.777 INFO lxc_conf - opened /var/lib/lxc/vs0/rootfs.hold as fd 20<br>
<br>
After I kill the lxc-start process there are many entries like<br>
vs0-1234 in /cgroup/lxc<br>
<br>
My configuration is as follows:<br>
<br>
Linux kontrabanda 3.10.17 #4 SMP Thu Jan 2 19:49:59 CET 2014 x86_64 Intel(R) Atom(TM) CPU D425 @ 1.80GHz GenuineIntel GNU/Linux<br>
<br>
<br>
# lxc-checkconfig<br>
--- Namespaces ---<br>
Namespaces: enabled<br>
Utsname namespace: enabled<br>
Ipc namespace: enabled<br>
Pid namespace: enabled<br>
User namespace: enabled<br>
Network namespace: enabled<br>
Multiple /dev/pts instances: enabled<br>
<br>
--- Control groups ---<br>
Cgroup: enabled<br>
Cgroup clone_children flag: enabled<br>
Cgroup device: enabled<br>
Cgroup sched: enabled<br>
Cgroup cpu account: enabled<br>
Cgroup memory controller: enabled<br>
Cgroup cpuset: enabled<br>
<br>
--- Misc ---<br>
Veth pair device: enabled<br>
Macvlan: enabled<br>
Vlan: enabled<br>
File capabilities: enabled<br>
<br>
<br>
# cat /var/lib/lxc/vs0/config<br>
# Template used to create this container: slackware<br>
# Template script checksum (SHA-1): 54f35064852a068c7ed1d0ae5e4b3ac8200ac790<br>
<br>
lxc.network.type = empty<br>
<br>
<br>
lxc.utsname = vs0<br>
<br>
lxc.mount = /var/lib/lxc/vs0/rootfs/etc/fstab<br>
<br>
lxc.tty = 4<br>
lxc.pts = 1024<br>
lxc.rootfs = /var/lib/lxc/vs0/rootfs<br>
<br>
lxc.cgroup.devices.deny = a<br>
# /dev/null and zero<br>
lxc.cgroup.devices.allow = c 1:3 rwm<br>
lxc.cgroup.devices.allow = c 1:5 rwm<br>
# consoles<br>
lxc.cgroup.devices.allow = c 5:1 rwm<br>
lxc.cgroup.devices.allow = c 5:0 rwm<br>
lxc.cgroup.devices.allow = c 4:0 rwm<br>
lxc.cgroup.devices.allow = c 4:1 rwm<br>
# /dev/{,u}random<br>
lxc.cgroup.devices.allow = c 1:9 rwm<br>
lxc.cgroup.devices.allow = c 1:8 rwm<br>
lxc.cgroup.devices.allow = c 136:* rwm<br>
lxc.cgroup.devices.allow = c 5:2 rwm<br>
# rtc<br>
lxc.cgroup.devices.allow = c 254:0 rwm<br>
<br>
# we don't trust root user in the container, better safe than sorry.<br>
# comment out only if you know what you're doing.<br>
lxc.cap.drop = sys_module mknod<br>
lxc.cap.drop = mac_override kill sys_time<br>
lxc.cap.drop = setfcap setpcap sys_boot<br>
<br>
# if you want to be even more restrictive with your container's root<br>
# user comment the three lines above and uncomment the following one<br>
# lxc.cap.drop=sys_admin<br>
<br>
<br>
# cat /var/lib/lxc/vs0/rootfs/etc/fstab<br>
lxcpts /var/lib/lxc/vs0/rootfs/dev/pts devpts defaults,newinstance 0 0<br>
none /var/lib/lxc/vs0/rootfs/proc proc defaults 0 0<br>
none /var/lib/lxc/vs0/rootfs/sys sysfs defaults 0 0<br>
none /dev/shm tmpfs defaults 0 0<br>
<br>
<br>
# mount | grep cgroup<br>
cgroup on /cgroup type cgroup (rw)<br>
<br>
<br><br>---------- Forwarded message ----------<br>From: Kevin Wilson <<a href="mailto:wkevils@gmail.com">wkevils@gmail.com</a>><br>To: LXC users mailing-list <<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a>><br>
Cc: <br>Date: Fri, 3 Jan 2014 11:42:26 +0200<br>Subject: [lxc-users] Cannot stop busybox container<br>Hello, lxc-users,<br>
<br>
I work with latest lxc from git.<br>
I created a busybox container (with -t busybox).<br>
<br>
I create a bridge on the host (virbr0).<br>
When I start the busybox container, I see:<br>
<br>
udhcpc (v1.19.4) started<br>
Sending discover...<br>
Sending discover...<br>
Sending discover...<br>
...<br>
and many more "Sending discover..." messages.<br>
<br>
There is no DHCP server in the LAN.<br>
I have two questions:<br>
1) Is it possible to configure the busybox container so that it will not<br>
start that udhcpc daemon and/or that it will not try to send these<br>
DHCP discover messages ? \<br>
2) I try to stop the busybox container (which is called busyboxCT) with<br>
lxc-stop -n busyboxCT<br>
and I wait over 10 minutes and it was not stopped, and the DHCP<br>
messages were still sent out from it.<br>
Is there a way to stop that container in such a case?<br>
<br>
regards,<br>
Kevin<br>
<br>
<br><br>---------- Forwarded message ----------<br>From: Giuseppe Tofoni <<a href="mailto:gt0057@gmail.com">gt0057@gmail.com</a>><br>To: LXC users mailing-list <<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a>><br>
Cc: <br>Date: Fri, 3 Jan 2014 12:03:31 +0100<br>Subject: Re: [lxc-users] lxc-start hangs with no output<br><div dir="ltr"><div><span name="Piotr Isajew">Hi, Piotr<br></span><br><span lang="en"><span>One possible solution</span> <span>is to not</span> <span>mount /</span><span>cgroup</span> <span>in</span> <span>fstab</span> <span>on the host.<br>
<br></span></span></div><div><span lang="en"><span>My configuration:<br></span></span></div><div><span lang="en"><span>Slackware 14.1<br></span></span></div>
<div><span lang="en"><span>lxc version 0.9.0<br></span></span></div><div><span lang="en"><span>kernel 3.12.5<br><br></span></span></div><div><span lang="en"><span>try it and good luck<br>
<br></span></span></div><div><span lang="en"><span>Giuseppe<br></span></span></div><span lang="en"><span><br></span></span></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2014/1/3 Piotr Isajew <span dir="ltr"><<a href="mailto:pki@ex.com.pl" target="_blank">pki@ex.com.pl</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I wanted do try out lxc on Slackware 14.1 64-bit. lxc-create<br>
works without problems. I'm however unable to start a container.<br>
<br>
After I do i.e.:<br>
<br>
lxc-start -n vs0<br>
<br>
the command just hangs with no output, consuming all the CPU<br>
resources and eventually eating up all the memory.<br>
<br>
I've spent last three days trying to get it work but I think I've<br>
ran out of ideas.<br>
<br>
<br>
log file contains:<br>
<br>
lxc-start 1388667324.768 INFO lxc_start_ui - using rcfile /var/lib/lxc/vs0/config<br>
lxc-start 1388667324.769 INFO lxc_apparmor - apparmor_load - apparmor is disabled<br>
lxc-start 1388667324.770 DEBUG lxc_conf - allocated pty '/dev/pts/2' (5/6)<br>
lxc-start 1388667324.771 DEBUG lxc_conf - allocated pty '/dev/pts/3' (7/8)<br>
lxc-start 1388667324.771 DEBUG lxc_conf - allocated pty '/dev/pts/4' (9/10)<br>
lxc-start 1388667324.771 DEBUG lxc_conf - allocated pty '/dev/pts/5' (11/12)<br>
lxc-start 1388667324.771 INFO lxc_conf - tty's configured<br>
lxc-start 1388667324.771 DEBUG lxc_console - using '/tmp/console.log' as console log<br>
lxc-start 1388667324.771 DEBUG lxc_console - using '/dev/tty' as console<br>
lxc-start 1388667324.771 DEBUG lxc_start - sigchild handler set<br>
lxc-start 1388667324.771 INFO lxc_start - 'vs0' is initialized<br>
lxc-start 1388667324.777 DEBUG lxc_start - Not dropping cap_sys_boot or watching utmp<br>
<br>
lxc-start 1388667324.777 INFO lxc_conf - opened /var/lib/lxc/vs0/rootfs.hold as fd 20<br>
<br>
After I kill the lxc-start process there are many entries like<br>
vs0-1234 in /cgroup/lxc<br>
<br>
My configuration is as follows:<br>
<br>
Linux kontrabanda 3.10.17 #4 SMP Thu Jan 2 19:49:59 CET 2014 x86_64 Intel(R) Atom(TM) CPU D425 @ 1.80GHz GenuineIntel GNU/Linux<br>
<br>
<br>
# lxc-checkconfig<br>
--- Namespaces ---<br>
Namespaces: enabled<br>
Utsname namespace: enabled<br>
Ipc namespace: enabled<br>
Pid namespace: enabled<br>
User namespace: enabled<br>
Network namespace: enabled<br>
Multiple /dev/pts instances: enabled<br>
<br>
--- Control groups ---<br>
Cgroup: enabled<br>
Cgroup clone_children flag: enabled<br>
Cgroup device: enabled<br>
Cgroup sched: enabled<br>
Cgroup cpu account: enabled<br>
Cgroup memory controller: enabled<br>
Cgroup cpuset: enabled<br>
<br>
--- Misc ---<br>
Veth pair device: enabled<br>
Macvlan: enabled<br>
Vlan: enabled<br>
File capabilities: enabled<br>
<br>
<br>
# cat /var/lib/lxc/vs0/config<br>
# Template used to create this container: slackware<br>
# Template script checksum (SHA-1): 54f35064852a068c7ed1d0ae5e4b3ac8200ac790<br>
<br>
lxc.network.type = empty<br>
<br>
<br>
lxc.utsname = vs0<br>
<br>
lxc.mount = /var/lib/lxc/vs0/rootfs/etc/fstab<br>
<br>
lxc.tty = 4<br>
lxc.pts = 1024<br>
lxc.rootfs = /var/lib/lxc/vs0/rootfs<br>
<br>
lxc.cgroup.devices.deny = a<br>
# /dev/null and zero<br>
lxc.cgroup.devices.allow = c 1:3 rwm<br>
lxc.cgroup.devices.allow = c 1:5 rwm<br>
# consoles<br>
lxc.cgroup.devices.allow = c 5:1 rwm<br>
lxc.cgroup.devices.allow = c 5:0 rwm<br>
lxc.cgroup.devices.allow = c 4:0 rwm<br>
lxc.cgroup.devices.allow = c 4:1 rwm<br>
# /dev/{,u}random<br>
lxc.cgroup.devices.allow = c 1:9 rwm<br>
lxc.cgroup.devices.allow = c 1:8 rwm<br>
lxc.cgroup.devices.allow = c 136:* rwm<br>
lxc.cgroup.devices.allow = c 5:2 rwm<br>
# rtc<br>
lxc.cgroup.devices.allow = c 254:0 rwm<br>
<br>
# we don't trust root user in the container, better safe than sorry.<br>
# comment out only if you know what you're doing.<br>
lxc.cap.drop = sys_module mknod<br>
lxc.cap.drop = mac_override kill sys_time<br>
lxc.cap.drop = setfcap setpcap sys_boot<br>
<br>
# if you want to be even more restrictive with your container's root<br>
# user comment the three lines above and uncomment the following one<br>
# lxc.cap.drop=sys_admin<br>
<br>
<br>
# cat /var/lib/lxc/vs0/rootfs/etc/fstab<br>
lxcpts /var/lib/lxc/vs0/rootfs/dev/pts devpts defaults,newinstance 0 0<br>
none /var/lib/lxc/vs0/rootfs/proc proc defaults 0 0<br>
none /var/lib/lxc/vs0/rootfs/sys sysfs defaults 0 0<br>
none /dev/shm tmpfs defaults 0 0<br>
<br>
<br>
# mount | grep cgroup<br>
cgroup on /cgroup type cgroup (rw)<br>
_______________________________________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org" target="_blank">lxc-users@lists.linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br>
</blockquote></div><br></div>
<br><br>---------- Forwarded message ----------<br>From: Piotr Isajew <<a href="mailto:pki@ex.com.pl">pki@ex.com.pl</a>><br>To: <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
Cc: <br>Date: Fri, 3 Jan 2014 12:31:05 +0100<br>Subject: Re: [lxc-users] lxc-start hangs with no output<br>On Fri, Jan 03, 2014 at 12:03:31PM +0100, Giuseppe Tofoni wrote:<br>
<br>
> One possible solution is to not mount /cgroup in fstab on the<br>
> host.<br>
<br>
Thank you Giuseppe. Following your advice solved that problem.<br>
<br>
Have a nice day :)<br>
<br>
Piotr<br>
<br>
<br>_______________________________________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a><br></blockquote></div>