Description of problem: lxc-create -n debian -t debian Version-Release number of selected component (if applicable): fedora 20 fully updated, and after reboot How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: W: Failure trying to run: chroot /var/cache/lxc/debian/partial-squeeze-amd64 mount -t proc proc /proc W: See /var/cache/lxc/debian/partial-squeeze-amd64/debootstrap/debootstrap.log for details Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: failed to execute template 'debian' lxc-create: aborted Expected results: The container should be created under /var/lib/lxc/debian Additional info: The command runs for a minute or more and downloads a lot of files, but finally it blows up. I am sure this bug will go to the new RHEL7 unless we fix it here.
Works here with upstream builds, 1.0.3 and git build from lxc master.
lxc-1.0.5-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/lxc-1.0.5-2.el6
lxc-1.0.5-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/lxc-1.0.5-2.fc19
lxc-1.0.5-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/lxc-1.0.5-2.fc20
Package lxc-1.0.5-2.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing lxc-1.0.5-2.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2167/lxc-1.0.5-2.el6 then log in and leave karma (feedback).
lxc-1.0.5-3.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-1.0.5-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
lxc-1.0.5-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.