[lxc-devel] [ lxc-Bugs-2958037 ] lxc-cgroup fails to output large files
Bugs item #2958037, was opened at 2010-02-24 16:49 Message generated for change (Tracker Item Submitted) made by legoater You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2958037&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: lxc cli Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Cedric Le Goater (legoater) Assigned to: Nobody/Anonymous (nobody) Summary: lxc-cgroup fails to output large files Initial Comment: lxc-cgroup uses a 4096 bytes buffer to which is too small to output large files. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2958037&group_id=163076 -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-2958234 ] network devices are not deleted on error
Bugs item #2958234, was opened at 2010-02-24 22:55 Message generated for change (Tracker Item Submitted) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2958234&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Daniel Lezcano (dlezcano) Assigned to: Daniel Lezcano (dlezcano) Summary: network devices are not deleted on error Initial Comment: If an error occurs when starting the container, after creating the interfaces but before assigning them to the container, the error code path does not take care to delete these interfaces and they stay in the system. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2958234&group_id=163076 -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-2958234 ] network devices are not deleted on error
Bugs item #2958234, was opened at 2010-02-24 22:55 Message generated for change (Settings changed) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2958234&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Daniel Lezcano (dlezcano) Assigned to: Daniel Lezcano (dlezcano) Summary: network devices are not deleted on error Initial Comment: If an error occurs when starting the container, after creating the interfaces but before assigning them to the container, the error code path does not take care to delete these interfaces and they stay in the system. -- >Comment By: Daniel Lezcano (dlezcano) Date: 2010-02-25 10:26 Message: Fixed by commit: http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commit;h=7fef7a06d809334b178f76630bb10faa16dc58c0 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2958234&group_id=163076 -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-2962063 ] Building man pages fails
Bugs item #2962063, was opened at 2010-03-02 18:32 Message generated for change (Tracker Item Submitted) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2962063&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Daniel Lezcano (dlezcano) Assigned to: Nobody/Anonymous (nobody) Summary: Building man pages fails Initial Comment: Hy there! I wanted to ask this for some time now, but only today I've made some time... So... My context: * ArchLinux (latest); * db2x_xsltproc (part of docbook2X 0.8.8) $Revision: 1.5 $ $Date: 2004/08/18 14:21:52 $ * /usr/bin/docbook2man (part of docbook2X 0.8.8) $Revision: 1.12 $ $Date: 2006/04/14 17:29:04 $ * I can't find anywhere the `-w` option in `man docbook2man` When building the man pages I get the following errors: ./autogen.sh ./configure cd ./doc make lxc-create.1 docbook2man -w lxc-create.sgml /usr//bin/db2x_xsltproc: Unknown option: w Try "/usr//bin/db2x_xsltproc --help" for more information. Unable to recognise encoding of this document at /usr/share/perl5/vendor_perl/XML/SAX/PurePerl/EncodingDetect.pm line 100. Document requires an element [Ln: 1, Col: 0] make: *** [lxc-create.1] Error 9 First fix-up: eliminate the `-w` from the Makefile: make lxc-create.1 cd .. && /bin/sh /home/ciprian/desktop/workbench/lxc/config/missing --run automake-1.11 --gnu doc/Makefile cd .. && /bin/sh ./config.status doc/Makefile config.status: creating doc/Makefile docbook2man lxc-create.sgml lxc-create.sgml:26: parser error : SystemLiteral " or ' expected https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2962063&group_id=163076 -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-2962063 ] Building man pages fails
Bugs item #2962063, was opened at 2010-03-02 19:32 Message generated for change (Comment added) made by ciprian_craciun You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2962063&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Daniel Lezcano (dlezcano) Assigned to: Nobody/Anonymous (nobody) Summary: Building man pages fails Initial Comment: Hy there! I wanted to ask this for some time now, but only today I've made some time... So... My context: * ArchLinux (latest); * db2x_xsltproc (part of docbook2X 0.8.8) $Revision: 1.5 $ $Date: 2004/08/18 14:21:52 $ * /usr/bin/docbook2man (part of docbook2X 0.8.8) $Revision: 1.12 $ $Date: 2006/04/14 17:29:04 $ * I can't find anywhere the `-w` option in `man docbook2man` When building the man pages I get the following errors: ./autogen.sh ./configure cd ./doc make lxc-create.1 docbook2man -w lxc-create.sgml /usr//bin/db2x_xsltproc: Unknown option: w Try "/usr//bin/db2x_xsltproc --help" for more information. Unable to recognise encoding of this document at /usr/share/perl5/vendor_perl/XML/SAX/PurePerl/EncodingDetect.pm line 100. Document requires an element [Ln: 1, Col: 0] make: *** [lxc-create.1] Error 9 First fix-up: eliminate the `-w` from the Makefile: make lxc-create.1 cd .. && /bin/sh /home/ciprian/desktop/workbench/lxc/config/missing --run automake-1.11 --gnu doc/Makefile cd .. && /bin/sh ./config.status doc/Makefile config.status: creating doc/Makefile docbook2man lxc-create.sgml lxc-create.sgml:26: parser error : SystemLiteral " or ' expected http://gitorious.org/~ciprian.craciun/lxc/ciprian-craciun-patches/commit/7a6e4fe2cc8fa7ea1c2a1e16a292a896717552b4?diffmode=sidebyside ------ You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2962063&group_id=163076 -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-2969963 ] lxc doesn't chroot
Bugs item #2969963, was opened at 2010-03-13 19:36 Message generated for change (Tracker Item Submitted) made by greenrd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2969963&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: lxc cli Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Robin Green (greenrd) Assigned to: Nobody/Anonymous (nobody) Summary: lxc doesn't chroot Initial Comment: Description of problem: lxc execute ignores the chroot I have specified - it runs the specified command in the "real" root. Version-Release number of selected component (if applicable): lxc-0.6.5-1.fc13.i686 How reproducible: Always Steps to Reproduce: 1. mkdir /cgroup 2. mount -t cgroup cgroup /cgroup 3. mkdir /var/lib/lxc 4. create a lxc.conf file like the following: lxc.rootfs=/var/lib/mach/roots/fedora-development-i386-core lxc.mount.entry=/dev /var/lib/mach/roots/fedora-development-i386-core/dev none rw,bind 0 0 lxc.mount.entry=/dev/pts /var/lib/mach/roots/fedora-development-i386-core/dev/pts none rw,bind 0 0 5. populate the chroot 6. lxc-create -n bug -f lxc.conf 7. lxc-execute -n bug /bin/bash 8. ls / Actual results: contents of "real" root displayed Expected results: contents of my chroot displayed Additional info: I tried to step through lxc-execute in gdb to debug it, but my attempts to set breakpoints in the cloned process didn't work. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2969963&group_id=163076 -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-2992198 ] ro flag not preserved for rootfs
Bugs item #2992198, was opened at 2010-04-26 10:28 Message generated for change (Tracker Item Submitted) made by ekatalog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2992198&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tefnet (ekatalog) Assigned to: Nobody/Anonymous (nobody) Summary: ro flag not preserved for rootfs Initial Comment: Setting root directory options to bind,ro in lxc.mount.entry results in a writable rootfs. This is caused by https://bugzilla.kernel.org/show_bug.cgi?id=15739 Attached patch causes setup_rootfs() to check for readonly flag on the rootfs directory and apply it to mount options if needed. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2992198&group_id=163076 -- ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3065262 ] multiple console is broken on a system container
Bugs item #3065262, was opened at 2010-09-13 14:35 Message generated for change (Tracker Item Submitted) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3065262&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Daniel Lezcano (dlezcano) Assigned to: Nobody/Anonymous (nobody) Summary: multiple console is broken on a system container Initial Comment: It is not possible to get 2 console for a container. That happens because the command asking for a console disconnect after getting the console and this is interpreted by lxc-start as the console was release. The next console will get the same console which is already in use. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3065262&group_id=163076 -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3065271 ] daemonize container when releasing the console
Bugs item #3065271, was opened at 2010-09-13 14:49 Message generated for change (Tracker Item Submitted) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3065271&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Daniel Lezcano (dlezcano) Assigned to: Nobody/Anonymous (nobody) Summary: daemonize container when releasing the console Initial Comment: When the container is started without the --daemonize option, the shell stays there with a container console. It would be cool to detach the current tty when the container is started making it to daemonize. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3065271&group_id=163076 -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3065261 ] force architecture for container
Bugs item #3065261, was opened at 2010-09-13 14:32 Message generated for change (Tracker Item Submitted) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3065261&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Daniel Lezcano (dlezcano) Assigned to: Nobody/Anonymous (nobody) Summary: force architecture for container Initial Comment: With 32bits container running on a 64bits host, the autoconf + package update will compile/download for 64bits. The workaround is to launch with "setarch i686 lxc-start -n foo" Embed this in a lxc configuration option. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3065261&group_id=163076 -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3113612 ] lxc-* tools are vulnerable for arguments with spaces
Bugs item #3113612, was opened at 2010-11-20 20:23 Message generated for change (Tracker Item Submitted) made by socketpair You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3113612&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: lxc cli Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Марк (socketpair) Assigned to: Nobody/Anonymous (nobody) Summary: lxc-* tools are vulnerable for arguments with spaces Initial Comment: r...@mmarkk-work:/usr/bin# fgrep '$*' lxc* lxc-ls:ls $* $lxcpath lxc-ls: cd $mount_point; ls $* -d $active lxc-netstat:for i in $*; do lxc-netstat:exec /usr/bin/lxc-unshare -s MOUNT -- $0 -n $name --exec $* lxc-netstat:exec netstat $* lxc-setcap:set -- $(getopt dh $*) lxc-setcap:for i in $*; do lxc-setuid:set -- $(getopt dh $*) lxc-setuid:for i in $*; do $* should be converted to "$@" (yes, with quotes). so (for example) lxc-ls should be changed: ls "$@" "$lxcpath" The same for other arguments. In BASH, if xxx="abc def", some_cmd $xxx will expand to some_cmd "abc" "def" and some_cmd "$xxx" will be expanded to some_cmd "abc def" ------ You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3113612&group_id=163076 -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3165633 ] busybox template doesn't start properly
Bugs item #3165633, was opened at 2011-01-26 12:48 Message generated for change (Tracker Item Submitted) made by net147 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3165633&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jonathan Liu (net147) Assigned to: Nobody/Anonymous (nobody) Summary: busybox template doesn't start properly Initial Comment: OS: Arch Linux 32-bit /etc/init.d/rcS do not use full path to syslogd, mount and udhcpc executables. As busybox requires /proc mounted if CONFIG_BUSYBOX_EXEC_PATH="/proc/self/exe" to run these commands without full path, the full path should be used in the startup script as /proc is mounted later in the script. It also fails to start the machine if /lib64 does not exist on the host system as there is a mount entry for /lib64 in the config. The attached patch changes commands in /etc/init.d/rcS to use full path and adds a check for /lib64 on host before adding lib64 mount entries to config. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3165633&group_id=163076 -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3165633 ] busybox template doesn't start properly
Bugs item #3165633, was opened at 2011-01-26 02:48 Message generated for change (Comment added) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3165633&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Jonathan Liu (net147) Assigned to: Nobody/Anonymous (nobody) Summary: busybox template doesn't start properly Initial Comment: OS: Arch Linux 32-bit /etc/init.d/rcS do not use full path to syslogd, mount and udhcpc executables. As busybox requires /proc mounted if CONFIG_BUSYBOX_EXEC_PATH="/proc/self/exe" to run these commands without full path, the full path should be used in the startup script as /proc is mounted later in the script. It also fails to start the machine if /lib64 does not exist on the host system as there is a mount entry for /lib64 in the config. The attached patch changes commands in /etc/init.d/rcS to use full path and adds a check for /lib64 on host before adding lib64 mount entries to config. -- >Comment By: Daniel Lezcano (dlezcano) Date: 2011-02-01 22:31 Message: Fixed with commit: http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commit;h=b09ecaf30367648a246d2e01c3a288a7653cc613 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3165633&group_id=163076 -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3184193 ] IPv6 default route
Bugs item #3184193, was opened at 2011-02-16 23:09 Message generated for change (Tracker Item Submitted) made by punjab You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3184193&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: punjab (punjab) Assigned to: Nobody/Anonymous (nobody) Summary: IPv6 default route Initial Comment: LXC on debian squeeze up to date. One network card bridge br0. In squeeze container interfaces configured IPv4 an IPv6. When container start IPv4 works fine. IPv6 no, I don’t know why, but "ip -6 route show" don’t have default route. Connectivity start working when i run: ip -6 route add default via IPV6_ GATEWAY_ADDRESS dev eth0 In interfaces is line: gateway IPV6_ GATEWAY_ADDRESS Permanent solution is add to interfaces line after gateway: pre-up ip -6 route add default via IPV6_ GATEWAY_ADDRESS dev eth0 In host system works ipv6 gateway fine and default route is automatically present. In container is debootstraped minimal squeeze from template. I don’t know if this is Debian or LXC bug, or something else.. Thanks -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3184193&group_id=163076 -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-2958037 ] lxc-cgroup fails to output large files
Bugs item #2958037, was opened at 2010-02-24 16:49 Message generated for change (Settings changed) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2958037&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: lxc cli Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Cedric Le Goater (legoater) >Assigned to: Daniel Lezcano (dlezcano) Summary: lxc-cgroup fails to output large files Initial Comment: lxc-cgroup uses a 4096 bytes buffer to which is too small to output large files. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2958037&group_id=163076 -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3113612 ] lxc-* tools are vulnerable for arguments with spaces
Bugs item #3113612, was opened at 2010-11-20 16:23 Message generated for change (Settings changed) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3113612&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: lxc cli Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Марк (socketpair) Assigned to: Nobody/Anonymous (nobody) Summary: lxc-* tools are vulnerable for arguments with spaces Initial Comment: root@mmarkk-work:/usr/bin# fgrep '$*' lxc* lxc-ls:ls $* $lxcpath lxc-ls: cd $mount_point; ls $* -d $active lxc-netstat:for i in $*; do lxc-netstat:exec /usr/bin/lxc-unshare -s MOUNT -- $0 -n $name --exec $* lxc-netstat:exec netstat $* lxc-setcap:set -- $(getopt dh $*) lxc-setcap:for i in $*; do lxc-setuid:set -- $(getopt dh $*) lxc-setuid:for i in $*; do $* should be converted to "$@" (yes, with quotes). so (for example) lxc-ls should be changed: ls "$@" "$lxcpath" The same for other arguments. In BASH, if xxx="abc def", some_cmd $xxx will expand to some_cmd "abc" "def" and some_cmd "$xxx" will be expanded to some_cmd "abc def" ------ You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3113612&group_id=163076 -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-2969963 ] lxc doesn't chroot
Bugs item #2969963, was opened at 2010-03-13 20:36 Message generated for change (Settings changed) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2969963&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: lxc cli Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Robin Green (greenrd) Assigned to: Nobody/Anonymous (nobody) Summary: lxc doesn't chroot Initial Comment: Description of problem: lxc execute ignores the chroot I have specified - it runs the specified command in the "real" root. Version-Release number of selected component (if applicable): lxc-0.6.5-1.fc13.i686 How reproducible: Always Steps to Reproduce: 1. mkdir /cgroup 2. mount -t cgroup cgroup /cgroup 3. mkdir /var/lib/lxc 4. create a lxc.conf file like the following: lxc.rootfs=/var/lib/mach/roots/fedora-development-i386-core lxc.mount.entry=/dev /var/lib/mach/roots/fedora-development-i386-core/dev none rw,bind 0 0 lxc.mount.entry=/dev/pts /var/lib/mach/roots/fedora-development-i386-core/dev/pts none rw,bind 0 0 5. populate the chroot 6. lxc-create -n bug -f lxc.conf 7. lxc-execute -n bug /bin/bash 8. ls / Actual results: contents of "real" root displayed Expected results: contents of my chroot displayed Additional info: I tried to step through lxc-execute in gdb to debug it, but my attempts to set breakpoints in the cloned process didn't work. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2969963&group_id=163076 -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3065262 ] multiple console is broken on a system container
Bugs item #3065262, was opened at 2010-09-13 14:35 Message generated for change (Settings changed) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3065262&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Daniel Lezcano (dlezcano) >Assigned to: Daniel Lezcano (dlezcano) Summary: multiple console is broken on a system container Initial Comment: It is not possible to get 2 console for a container. That happens because the command asking for a console disconnect after getting the console and this is interpreted by lxc-start as the console was release. The next console will get the same console which is already in use. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3065262&group_id=163076 -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-2992198 ] ro flag not preserved for rootfs
Bugs item #2992198, was opened at 2010-04-26 10:28 Message generated for change (Settings changed) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2992198&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None Status: Open >Resolution: Remind Priority: 5 Private: No Submitted By: Tefnet (ekatalog) >Assigned to: Daniel Lezcano (dlezcano) Summary: ro flag not preserved for rootfs Initial Comment: Setting root directory options to bind,ro in lxc.mount.entry results in a writable rootfs. This is caused by https://bugzilla.kernel.org/show_bug.cgi?id=15739 Attached patch causes setup_rootfs() to check for readonly flag on the rootfs directory and apply it to mount options if needed. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2992198&group_id=163076 -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-2962063 ] Building man pages fails
Bugs item #2962063, was opened at 2010-03-02 18:32 Message generated for change (Settings changed) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2962063&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: Daniel Lezcano (dlezcano) Assigned to: Nobody/Anonymous (nobody) Summary: Building man pages fails Initial Comment: Hy there! I wanted to ask this for some time now, but only today I've made some time... So... My context: * ArchLinux (latest); * db2x_xsltproc (part of docbook2X 0.8.8) $Revision: 1.5 $ $Date: 2004/08/18 14:21:52 $ * /usr/bin/docbook2man (part of docbook2X 0.8.8) $Revision: 1.12 $ $Date: 2006/04/14 17:29:04 $ * I can't find anywhere the `-w` option in `man docbook2man` When building the man pages I get the following errors: ./autogen.sh ./configure cd ./doc make lxc-create.1 docbook2man -w lxc-create.sgml /usr//bin/db2x_xsltproc: Unknown option: w Try "/usr//bin/db2x_xsltproc --help" for more information. Unable to recognise encoding of this document at /usr/share/perl5/vendor_perl/XML/SAX/PurePerl/EncodingDetect.pm line 100. Document requires an element [Ln: 1, Col: 0] make: *** [lxc-create.1] Error 9 First fix-up: eliminate the `-w` from the Makefile: make lxc-create.1 cd .. && /bin/sh /home/ciprian/desktop/workbench/lxc/config/missing --run automake-1.11 --gnu doc/Makefile cd .. && /bin/sh ./config.status doc/Makefile config.status: creating doc/Makefile docbook2man lxc-create.sgml lxc-create.sgml:26: parser error : SystemLiteral " or ' expected http://gitorious.org/~ciprian.craciun/lxc/ciprian-craciun-patches/commit/7a6e4fe2cc8fa7ea1c2a1e16a292a896717552b4?diffmode=sidebyside ------ You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2962063&group_id=163076 -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-2969963 ] lxc doesn't chroot
Bugs item #2969963, was opened at 2010-03-13 20:36 Message generated for change (Settings changed) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2969963&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: lxc cli Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Robin Green (greenrd) >Assigned to: Daniel Lezcano (dlezcano) Summary: lxc doesn't chroot Initial Comment: Description of problem: lxc execute ignores the chroot I have specified - it runs the specified command in the "real" root. Version-Release number of selected component (if applicable): lxc-0.6.5-1.fc13.i686 How reproducible: Always Steps to Reproduce: 1. mkdir /cgroup 2. mount -t cgroup cgroup /cgroup 3. mkdir /var/lib/lxc 4. create a lxc.conf file like the following: lxc.rootfs=/var/lib/mach/roots/fedora-development-i386-core lxc.mount.entry=/dev /var/lib/mach/roots/fedora-development-i386-core/dev none rw,bind 0 0 lxc.mount.entry=/dev/pts /var/lib/mach/roots/fedora-development-i386-core/dev/pts none rw,bind 0 0 5. populate the chroot 6. lxc-create -n bug -f lxc.conf 7. lxc-execute -n bug /bin/bash 8. ls / Actual results: contents of "real" root displayed Expected results: contents of my chroot displayed Additional info: I tried to step through lxc-execute in gdb to debug it, but my attempts to set breakpoints in the cloned process didn't work. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=2969963&group_id=163076 -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3198796 ] Eth device renamed on stop
Bugs item #3198796, was opened at 2011-03-03 20:08 Message generated for change (Settings changed) made by dlezcano You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3198796&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: liblxc Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Daniel Lezcano (dlezcano) Summary: Eth device renamed on stop Initial Comment: I have to use the lxc.network.type=phys for my container networking. When shutting down the container the host device name change to dev3 where it was eth1 before. I can consistently reproduce this. If the host device was eth2 it will be renamed to dev4 upon shutting down the container. Anyone seen this one? -Riaan -- Comment By: Daniel Lezcano (dlezcano) Date: 2011-03-03 20:41 Message: I see exactly what and where is the problem. I will fix it. Thanks for reporting. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3198796&group_id=163076 -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3276038 ] lxc-attach fails on kernel with the setns feature
Bugs item #3276038, was opened at 2011-04-05 13:53 Message generated for change (Tracker Item Submitted) made by legoater You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3276038&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None Status: Open Resolution: None Priority: 3 Private: No Submitted By: Cedric Le Goater (legoater) Assigned to: Nobody/Anonymous (nobody) Summary: lxc-attach fails on kernel with the setns feature Initial Comment: when running the lxc -attach command on a kernel patched with the setns syscall, it fails with the following message : lxc-attach: Does this kernel version support 'attach' ? lxc-attach: failed to enter the namespace it seems that the check done in commit : http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commit;h=9f53d717c4fea7bb2a493d911da0abbe9c78aef5 is too strong. Please see attached patch for a possible fix. Thanks, -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3276038&group_id=163076 -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3276038 ] lxc-attach fails on kernel with the setns feature
Bugs item #3276038, was opened at 2011-04-05 13:53 Message generated for change (Settings changed) made by legoater You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3276038&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: liblxc Group: None Status: Open Resolution: None Priority: 3 Private: No Submitted By: Cedric Le Goater (legoater) >Assigned to: Cedric Le Goater (legoater) Summary: lxc-attach fails on kernel with the setns feature Initial Comment: when running the lxc -attach command on a kernel patched with the setns syscall, it fails with the following message : lxc-attach: Does this kernel version support 'attach' ? lxc-attach: failed to enter the namespace it seems that the check done in commit : http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commit;h=9f53d717c4fea7bb2a493d911da0abbe9c78aef5 is too strong. Please see attached patch for a possible fix. Thanks, -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3276038&group_id=163076 -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3357704 ] lxc-init fails with shared root fs on Fedora 15
Bugs item #3357704, was opened at 2011-07-07 15:42 Message generated for change (Tracker Item Submitted) made by moschny You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3357704&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Thomas Moschny (moschny) Assigned to: Nobody/Anonymous (nobody) Summary: lxc-init fails with shared root fs on Fedora 15 Initial Comment: See https://bugzilla.redhat.com/show_bug.cgi?id=694931: # lxc-create -n foo # lxc-execute -n foo /bin/bash lxc-init: failed to mount /dev/mqueue : Too many levels of symbolic links The direct reason is that /dev/mqueue is mounted with type autofs by systemd. In the end however it is unclear whether lxc_init should try to mount this at all, see later comments in the mentioned bug. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3357704&group_id=163076 -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3388933 ] Script lxc-debian don't create /dev/shm/network
Bugs item #3388933, was opened at 2011-08-09 16:48 Message generated for change (Tracker Item Submitted) made by vazhnov You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3388933&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Alexey Vazhnov (vazhnov) Assigned to: Nobody/Anonymous (nobody) Summary: Script lxc-debian don't create /dev/shm/network Initial Comment: Sorry for my English. Host system: Debian6 amd64 lxc 0.7.2-1 I take script lxc-debian from lxc-0.7.4.1 (rename lxc-debian.in to lxc-squeeze and replace all «@LOCALSTATEDIR@» to «/var») because I need Debian squeeze in LXC. When I start lxc: Configuring network interfaces...ifup: failed to open statefile /etc/network/run/ifstate: No such file or directory /etc/network/run/ — symlink to /dev/shm/network Then I run: mkdir /dev/shm/network and problem solved. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3388933&group_id=163076 -- uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
[lxc-devel] [ lxc-Bugs-3388933 ] Script lxc-debian don't create /dev/shm/network
Bugs item #3388933, was opened at 2011-08-09 16:48 Message generated for change (Comment added) made by vazhnov You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3388933&group_id=163076 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Alexey Vazhnov (vazhnov) Assigned to: Nobody/Anonymous (nobody) Summary: Script lxc-debian don't create /dev/shm/network Initial Comment: Sorry for my English. Host system: Debian6 amd64 lxc 0.7.2-1 I take script lxc-debian from lxc-0.7.4.1 (rename lxc-debian.in to lxc-squeeze and replace all «@LOCALSTATEDIR@» to «/var») because I need Debian squeeze in LXC. When I start lxc: Configuring network interfaces...ifup: failed to open statefile /etc/network/run/ifstate: No such file or directory /etc/network/run/ — symlink to /dev/shm/network Then I run: mkdir /dev/shm/network and problem solved. -- >Comment By: Alexey Vazhnov (vazhnov) Date: 2011-08-09 17:47 Message: After guest restarting, directory is absent again. Not so simple :( -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=826303&aid=3388933&group_id=163076 -- uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
