| Summary: | LXC templates not working | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Herbert Poetzl <herbert> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | mageia, marja11, sharpzq4300, thierry.vignaud |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | lxc-1.0.5-3.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Herbert Poetzl
2015-07-26 09:04:48 CEST
David Walser
2015-07-30 18:26:32 CEST
CC:
(none) =>
mageia, thierry.vignaud I've tested on Cauldron. You can add -x to the shebang on /usr/share/lxc/templates/ in order to debug. FC one failed b/c of network issue (I've seen that too but it works fine else) You need to install dnf-yum though Debian works if you install deboostrap. ... It would be better if upstream lxc would have templates that work on every platforms (eg: FC one downloads a squashfs image if yum isn't availlable) Assigning to all packagers collectively since there is no registered maintainer for this package. Assignee:
bugsquad =>
pkg-bugs The primary problem here is that the package managers are not installed for each distro being installed (the network issue and 404 error are of lesser significance) I've been messing around with LXC and what I have found is that the templates work fine as long as the host and guest are the same distro. For example, the lxc-fedora template installs fine under Fedora. This is because the host has the correct package manager. It isn't so much of a bug in the LXC templates, the issue is more that the OS doesn't install every single package manager as a dependency for LXC. Now I don't think it is really efficient to install every single package manager upon installing LXC. What I think *should* happen is that the templates do a better pre-installation checklist, the same way ./configure checks the system thoroughly before doing a compile in a properly set-up source package. And after doing a better check, the templates should provide a better explanation of what the user needs to do to get it working. CC:
(none) =>
sharpzq4300 Hi Herbert, Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we were waiting for the big Plasma5 update in Mageia 6, that fixed many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. CC:
(none) =>
marja11 No reply, so closing as OLD since Mageia 5 is no longer maintained. Resolution:
(none) =>
OLD |