https://bugzilla.novell.com/show_bug.cgi?id=832337 https://bugzilla.novell.com/show_bug.cgi?id=832337#c FeiXiang Zhang changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |ms@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832337 https://bugzilla.novell.com/show_bug.cgi?id=832337#c2 Yarny Yarny changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Yarny@public-files.de | --- Comment #2 from Yarny Yarny 2013-08-14 22:22:51 UTC --- I put a perl breakpoint in KIWIGlobals.pm in the function callContained, just before the second lxc-execute (that is line 836 here). Then I manually called the lxc-execute command -> Nothing. The perl debugger says $lxcinit=$root/usr/lib64/lxc/lxc-init, and indeed this file contains my config.sh. So kiwi copied config.sh into $root/usr/lib64/lxc/lxc-init, but it left $root/usr/lib/lxc/lxc-init untouched. Then I did $ cp $root/usr/lib{64,}/lxc/lxc-init and called the lxc-execute command again -> $root/config.sh.tag is created! It appears that lxc-execute uses /usr/lib/lxc/lxc-init even on 64bit systems whereas kiwi prepares /usr/lib64/lxc/lxc-init. The result is lxc-execute just executing true as instructed by kiwi, which certainly is successful but without effect. At this point I don't know how to proceed. The lxc manpage isn't very talkative about lxc-init and there is not lxc-init manpage. How is lxc-execute supposed to call lxc-init? BTW, another issue crossed my mind while reading the kiwi code. Is replacing lxc-init really the correct way to execute scripts in linux containers? I have almost no knowledge about linux container technology, but I appears to me that lxc-init, as it is provided by the lxc package, is not meant to be replaced by some user-provided script. Wouldn't the replacement of lxc-init in the image root break lxc-execute in the target system? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832337 https://bugzilla.novell.com/show_bug.cgi?id=832337#c4 --- Comment #4 from Marcus Schaefer 2013-08-15 08:08:13 UTC --- Created an attachment (id=552725) --> (http://bugzilla.novell.com/attachment.cgi?id=552725) use lxc-start to run scripts this is an untested first version of a patch. Would you mind to give it a try ? Thanks much -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832337 https://bugzilla.novell.com/show_bug.cgi?id=832337#c5 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|Yarny@public-files.de | Resolution| |FIXED --- Comment #5 from Marcus Schaefer 2013-08-15 13:05:17 UTC --- ok I tested and fixed the problem, the new function now uses plain lcx-start and does not fiddle with lxc-init, here is the commit for reference: commit f05ca4697c327948834cc26f587774096334a5c3 Author: Marcus Schäfer Date: Thu Aug 15 15:02:31 2013 +0200 - fixed kiwi script calls if they are done contained via lxc the callContained() function was changed to use the lxc-start tool to run the scripts instead of wrapping around lxc-init and calling lxc-execute (bnc #832337) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=832337 https://bugzilla.novell.com/show_bug.cgi?id=832337#c7 --- Comment #7 from Yarny Yarny 2013-08-15 13:25:23 UTC --- Created an attachment (id=552745) --> (http://bugzilla.novell.com/attachment.cgi?id=552745) Patch to use lxc-execute This patch fixes the lxc issue but retains lxc-execute as the "chroot-replacement". I have no idea if there is an advantage in using lxc-execute instead of lxc-start (besides the comments on the lxc-manpage), so feel free to ignore this patch as long as lxc-start works. Also, thanks for fixing this! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.