New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fedora template maintenance #1356
Labels
Feature
New feature, not a bug
Comments
I would vote for getting rid of the complexity. (@stgraber) |
|
Ok, thanks for your reply. I will work on a suggestion for a new template in the next few days and maybe also try out how this would work when converting a CloudImage. |
This was referenced Dec 24, 2016
The template has been completely reworked and merged. This can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I lately put some effort in creating community packages for LXD on Fedora and therefore I also had a look at the
lxc-fedora
template in LXC. It's a very feature rich template that still works fine also with newer Fedora releases but it hasn't seen much love lately (maybe because of its complexity?).To get know the template a bit better I ported the bootstrapping part for non-yum distributions from the currently used Fedora 20 squashfs image to the Fedora 24 image and therefore was able to get rid of some complexity (see my fedora branch). By dropping
python
(dnf
now requirespython-3
),yum
,rsyslog
andchkconfig
, I was able to reduce the image size from 230MB to around 160MB, what I think is a big win.However, the shift to
dnf
made me think of some issues with the current code paths that I would like to address here:Is it worth to put more effort in updating the
lxc-fedora
template or is this something that might not be widely used anymore with the availability of the Fedora CloudImages?Are there users which use this template to build containers of unsupported versions (non-
dnf
, non-systemd
) of Fedora?Getting rid of all this compatibility code for old Fedora versions would simplify the template quite a bit. Would you be interested if I put some effort in doing this?
Please let me know what you think.
The text was updated successfully, but these errors were encountered: