Great explanation, thanks a lot!
Thought thinking about it my dependancy for local/corporate level boxes is RHEL9 but for LIVE its Amazon Linux 2023 which is another story. 
Any advances on porting Incus to RHEL9/10 or Amazon Linux?
I’m stuck on LXD 5.23.3 LTS for production systems as it can be installed via SNAP but there is no way I can install Incus from packages currently.
I checked the Incus image repository. Here is what I found.
| os | release |
|---|---|
| Almalinux | 10 |
| Almalinux | 8 |
| Almalinux | 9 |
| Alpine | 3.19 |
| Alpine | 3.20 |
| Alpine | 3.21 |
| Alpine | 3.22 |
| Alpine | edge |
| Alt | Sisyphus |
| Alt | p11 |
| Amazonlinux | 2 |
| Amazonlinux | 2023 |
| Archlinux | current |
| Busybox | 1.36.1 |
| Centos | 9-Stream |
| Debian | bookworm |
| Debian | bullseye |
| Debian | forky |
| Debian | trixie |
| Devuan | chimaera |
| Devuan | daedalus |
| Fedora | 40 |
| Fedora | 41 |
| Fedora | 42 |
| Funtoo | next |
| Gentoo | current |
| Kali | current |
| Mint | ulyana |
| Mint | ulyssa |
| Mint | uma |
| Mint | una |
| Mint | vanessa |
| Mint | vera |
| Mint | victoria |
| Mint | virginia |
| Mint | wilma |
| Nixos | 25.05 |
| Nixos | unstable |
| Openeuler | 20.03 |
| Openeuler | 22.03 |
| Openeuler | 24.03 |
| Openeuler | 25.03 |
| Opensuse | 15.5 |
| Opensuse | 15.6 |
| Opensuse | tumbleweed |
| Openwrt | 22.03 |
| Openwrt | 23.05 |
| Openwrt | 24.10 |
| Openwrt | snapshot |
| Oracle | 7 |
| Oracle | 8 |
| Oracle | 9 |
| Plamo | 8.x |
| Rockylinux | 10 |
| Rockylinux | 8 |
| Rockylinux | 9 |
| Slackware | 15.0 |
| Slackware | current |
| Springdalelinux | 7 |
| Springdalelinux | 8 |
| Springdalelinux | 9 |
| Ubuntu | jammy |
| Ubuntu | noble |
| Ubuntu | oracular |
| Ubuntu | plucky |
| Voidlinux | current |
Looks promising, where can I find the incus repo?
The best way is with the Incus CLI. You can also take a look here.
I used Nushell to create the table.
incus image list images: --format json |
from json |
get properties |
select os release |
uniq |
to md --pretty
I’m trying to install incus not create an instance
These links might help. I use the Zabbly debian releases.
No incus package for Amazon Linux 2023 which means I will remain using LXD for the time being.
Static binaries are all very well but they are a MPITA with a cloud-init install.
The thread title should be something like “How can I get Incus packaged for RHEL or Amazon Linux?”.
You can surely compile Incus on RHEL or Amazon Linux. But you are looking for someone to package Incus for those distributions and make those packages available on the respective repositories.
Is this important enough that you may contribute towards the sponsorship of such an endeavor?
1 Like
Its simpler just to continue using LXD for the time being, There is nos business case for me to include Incus in our build system and install it on multiple architectures and distros when we already have that ability using snap install lxd.
You are right. I got mixed up because I did not reread the thread.
Thanks for getting us back on track.
Try following the instructions for Rocky Linux:
This uses COPR packages for the EPEL repository and should work on RHEL and derivatives.
That might work for RHEL9-10 but not RHEL8, unfortunately I don’t have any RHEL9-10 I can try it on. FYI:- End of life for RHEL8 is May 31 2029 so a while before customers stop using it.
Error: It wasn’t possible to enable this project.
Repository ‘epel-8-x86_64’ does not exist in project ‘neil/incus’.
Amazon Linux 2 is the worst, I suspect AWS ditched EPEL so people have to use the EC2 feature set for virtualisation. Nor is Amazon Linux 2 i compatible with current Fedora packages.
Now I’d be happy just to use a minimal Ubuntu base install for the base hosts but our customers dictate the OS they use so we have to support Amazon Linux 2.
I suppose you can approach those packagers and suggest to sponsor them to create Incus packages for RHEL8. Considering that EOL is 2029, it would be worthy effort.
If I had the time I’d do a Incus snap, Never seem to have the time.
The snap subsystem has the benefit of restricting the apps in very strict ways. However, tools like LXD cannot work with such restrictions. Therefore, the snap subsystem has a cheat code, the interface “lxd-support”, which makes the LXD package unconfined. This interface is part of the super-privileged interfaces (read more). In that URL there is a link that you follow to ask for approval by the Store.
If you want to create your own snap package and want the lxd-support interface for your package, you need to request it, and a person will evaluate your request. You may ask them now if they will grant you the lxd-support interface when you eventually create a snap package for Incus. There’s a high chance they say no. Here is where you ask for approval from the Store for the auto-connection of the “lxd-support” interface.
1 Like
Your not selling this to me Simos 
We build Incus RPMs for EL9 and EL10 for our AlmaLinux based hosting software. Maybe that could help you out?
As this is designed to match our needs, the data directory is set as /home/incus/ in these RPMs.
As for EL8: For us its not worth the hassles. Too many supporting libraries would need to be updated or outright supplied to get it working.
1 Like