Latest upstream release: 0.8.0 Current version in Fedora Rawhide: 0.7.5 URL: http://sourceforge.net/api/file/index/project-name/lxc/mtime/desc/limit/100/rss Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
@Thomas: are you taking care of this ?
(In reply to comment #1) > @Thomas: are you taking care of this ? Yes, will do. Was on a business trip.
Any ETA on this? Any chance on getting it updated before F18 is released?
Yes, should be ready until then.
Great.
Please update to 0.8.0 in Fedora 17/18 as soon as possible. The previous versions have a systemd incompatibility.
I have built lxc 0.8.0 in rawhide now. Alas, I also tested this version on my F18 machine and there are still problems with systemd. See for example http://sourceforge.net/tracker/?func=detail&aid=3559833&group_id=163076&atid=826303. So, I am not sure whether it is worth the effort creating F17 and F18 packages that also will not work properly. According to upstream, 0.9.0~alpha3 is soon to come, maybe we should wait for that.
The bug you referenced actually has an end user workaround -- change the existing filesystem mounts to private before starting any containers: mount --make-rprivate / (A more complete solution to dealing with shared mounts in lxc is being worked out on the mailing list.) I am able to use lxc 0.9.0.alpha2 successfully on Fedora 18 with the workaround above. However, lxc 0.7.5 and earlier have some more serious problems with cgroup handling which manifest when using systemd, and there is no end user workaround. See for example this fix to upstream that I made before 0.8.0: http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commit;h=1d39a0658370ac104825e796bf90bb96ae0b7027 Since the packages in the Fedora 17/18 repo would seem to be unusable to anyone, my suggestion would be to go ahead and update them to a version that at least operates correctly when using a known workaround. (Or in the worse case, this will at least help identify any other bugs that may still exist, so they can get fixed sooner rather than later...?)
Please update LXC. I am unable to anything with the current version of LXC shipped with Fedora.
Built a rpm for personal use from the staging branch https://github.com/lxc/lxc http://sagarun.fedorapeople.org/SRPMS/lxc-0.9.0a3-1.20130302git9958532.fc17.src.rpm http://koji.fedoraproject.org/koji/taskinfo?taskID=5069722
lxc-0.8.0-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/lxc-0.8.0-2.fc18
lxc-0.8.0-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/lxc-0.8.0-2.fc17
Package lxc-0.8.0-2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing lxc-0.8.0-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3330/lxc-0.8.0-2.fc17 then log in and leave karma (feedback).
(In reply to comment #13) > Package lxc-0.8.0-2.fc17: > * should fix your issue, > * was pushed to the Fedora 17 testing repository, > * should be available at your local mirror within two days. > Update it with: > # su -c 'yum update --enablerepo=updates-testing lxc-0.8.0-2.fc17' > as soon as you are able to. > Please go to the following url: > https://admin.fedoraproject.org/updates/FEDORA-2013-3330/lxc-0.8.0-2.fc17 > then log in and leave karma (feedback). Still doesn't solve the pivot_root problem lxc-start: Invalid argument - pivot_root syscall failed lxc-start: failed to setup pivot root lxc-start: failed to set rootfs for 'test.lxc.test.com' lxc-start: failed to setup the container lxc-start: invalid sequence number 1. expected 2 lxc-start: failed to spawn 'test.lxc.test.com'
(In reply to comment #14) > Still doesn't solve the pivot_root problem > > > lxc-start: Invalid argument - pivot_root syscall failed > lxc-start: failed to setup pivot root > lxc-start: failed to set rootfs for 'test.lxc.test.com' > lxc-start: failed to setup the container > lxc-start: invalid sequence number 1. expected 2 > lxc-start: failed to spawn 'test.lxc.test.com' Did you try the work around mentioned earlier (comment #8) in this ticket? mount --make-rprivate /
After doing mount --make-rprivate /. Things seems to work! Thanks.
Also 0.9.0 alpha3 doesn't require any workarounds for LXC to work. Can we backport related patches to 0.8.0?
(In reply to comment #17) > Also 0.9.0 alpha3 doesn't require any workarounds for LXC to work. Can we > backport related patches to 0.8.0? We could, but I am a bit hesitant to do that, as I can not really oversee side-effects this might have. Also, 0.9.0 now seems really round the corner.
I'm testing lxc-0.9.0rc1 Attached you can find the update spec file: - Update to 0.9.0rc1. - Update spec file to new upstream chages (ex. /etc/lxc/default, /usr/share/lxc/hooks) - Add rsync as dependency for Ubuntu and Debian templates. - Add docbook2X as build requirement. The RPMS and SRPM for Fedora 17 x86_64 are here: http://daniele.vigano.me/rpms/lxc-0.9.0rc1/
Created attachment 714550 [details] spec file for 0.9.0
Updated lxc 0.9.0 packages are here: http://thm.fedorapeople.org/lxc/ for all active Fedora branches, plus EPEL-6. Please test! Any comments are appreciated. If there are no objections, I will create official updates.
Hi, I have installed the F18 packages found here http://thm.fedorapeople.org/lxc/fedora-18/x86_64/ and tried to create a F18 guest with: lxc-create -t fedora -n test -- -R 18 At the end of the command I get some warnings: warning: Failed to read auxiliary vector, /proc not mounted? Also, when running lxc-start -n test I don't get any output, the console got frozen.. In principle this should be reproducible, since I used a fresh installation of F18 x86_64.
Hi, I have figured out that the problem was a missing option in the config: lxc.autodev = 1 This can be fixed in the lxc-fedora template. I have attached a patch that fixes that (autodev.patch). The patch is actually only a subset of a patch already proposed in the lxc-devel mailing list: http://sourceforge.net/mailarchive/forum.php?thread_name=1365372287.19430.26.camel%40canyon.wittsend.com&forum_name=lxc-devel
Created attachment 737699 [details] Patch to lxc-fedora which adds lxc.autodev =1
(In reply to comment #21) > Please test! 0.9.0 works for me. Well, the template is still buggy. Meaning not able to create Rawhide containers and set the root password but those are upstream issue.
(In reply to comment #25) > (In reply to comment #21) > > Please test! > > 0.9.0 works for me. > > Well, the template is still buggy. Meaning not able to create Rawhide > containers and set the root password but those are upstream issue. Also working well for me. About the template I'm working on a template for the latest Fedora: https://gist.github.com/daniviga/4682880#file-bootstrap-fedora18-sh
(In reply to Thomas Moschny from comment #21) > Updated lxc 0.9.0 packages are here: > http://thm.fedorapeople.org/lxc/ > for all active Fedora branches, plus EPEL-6. > > Please test! > > Any comments are appreciated. If there are no objections, I will create > official updates. I think checking that /usr/lib64/lxc/rootfs is not currently mounted would be a welcome addition. (I may have done something funky, but I think it caused the yum upgrade to fail.)
For me the LXC 0.9.0 packages provided by Thomas Moschny are working well also on Fedora 19 beta.
Hi, I have tried to create a container of the fresh released F19 on a F18 host with the lxc-0.9.0-1.fc18.x86_64 package but it fails: Fetching from http://ftp.uni-erlangen.de/pub/Linux/MIRROR.fedora/core/development/19/x86_64/os//Packages/f/fedora-release-19-1.noarch.rpm ..... curl: (22) The requested URL returned error: 404 Not Found Failed to download fedora release rpm ....... No repomd file Error: File /var/cache/lxc/fedora/x86_64/19/partial/var/cache/yum/x86_64/$releasever/fedora/metalink.xml does not exist Failed to download the rootfs, aborting. ... It looks like it is trying to download fedora-release-19-1.noarch.rpm, but the correct version which is in the repositories is fedora-release-19-2.noarch.rpm. Regards, Enrique
In the LXC mailing list there is a patch which fixed the problem I mentioned in the previous message: http://sourceforge.net/mailarchive/forum.php?thread_name=20130710155821.GA8005%40tp&forum_name=lxc-devel
Any news about the inclusion of LXC 0.9.0 in Fedora 19 (and maybe 18)? Version 0.8.0 is quite old, buggy and doesn't work out of the box. Thanks
I can help out with the packaging and builds. I use this package now and then. I have also raised a request for co-maintainer ship. Please review and approve.
I'm currently testing and using Thomas Moschny packages with success and working on a template for the latest Fedora (17/18/19) https://gist.github.com/daniviga/4682880#file-bootstrap-fedora18-sh. If help is needed I'm available too. Cheers
lxc-0.9.0-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/lxc-0.9.0-2.fc20
lxc-0.9.0-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/lxc-0.9.0-2.fc18
lxc-0.9.0-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/lxc-0.9.0-2.el6
lxc-0.9.0-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/lxc-0.9.0-2.fc19
This can be pushed! Works for me!
lxc-0.9.0-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
lxc-0.9.0-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
lxc-0.9.0-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
lxc-0.9.0-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.