Open abitrolly opened 5 years ago
Thanks for your interest. There was already a discussion about this a while ago, you can find it at ganto/copr-lxd#6. I don't think it's an easy task to do and honestly I'm not ready to be a maintainer for such a potentially critical infrastructure component. If someone else is stepping in, I'll definitely try to support where I can but I wouldn't want to lead such an effort.
Actually the current spec file is not complying with the Fedora packaging rules and it would remain to see how a client-only spec file would look like. But currently I don't have time to do such an effort because what is available in this repository is functional and good enough for me.
Upstream is providing lxd via snap and it seems that it can be used on Fedora too. So if you would want a supported way of using the lxd client, I guess that would be the way to go.
I used it as a snap
. It produces so many SELinux warnings that had to I uninstall both lxd
and snapd
. If packing lxd-client
is not so easy, maybe it is possible to put binary for amd64 Linux to https://github.com/ganto/copr-lxc3/releases ? It will be the same for all Linux versions, right?
If packing
lxd-client
is not so easy, maybe it is possible to put binary for amd64 Linux to https://github.com/ganto/copr-lxc3/releases?
One could build a static binary that would be compatible for all Linux amd64, but unfortunately this is completely out of scope of this repository. This repository is for RPM spec files which are built by the Fedora COPR build service. And that one is not able to produce random binaries that can be downloaded from Github, I'm sorry.
But you could suggest this to lxd upstream if they would offer a pre-built client, similar to the kubernetes or okd clients.
Btw. what in the first place is your issue with using the COPR repository? Using the COPR repository you can simply install the LXD client with dnf install lxd-client
.
I don't think it's an easy task to do and honestly I'm not ready to be a maintainer for such a potentially critical infrastructure component. If someone else is stepping in, I'll definitely try to support where I can but I wouldn't want to lead such an effort.
I don't know why you think this would be hard. You're doing it now. There's a Fedora Container SIG, so you could join that and work with them to help support LXD in Fedora officially. I'm sure folks like @cverna and @jcajka could help you with maintaining it in Fedora officially.
The SELinux policy works great with a distro-packaged LXD, so it's worth shipping the whole thing. :)
Hi @ganto. What do you think about making
lxd-client
available from official Fedora 29+ repositories? It is convenient to have it there for easy setup of remote access to LXD servers.