[SOLVED] Cant install numactl - Proxmox 9.1

mouse51180

New Member
Dec 10, 2025
2
0
1
I'm trying to install numactl, but am running down a rabbit hole of error messages.
Code:
root@pve-node0:~# apt-get update
Hit:1 http://download.proxmox.com/debian/ceph-squid trixie InRelease
Hit:2 http://download.proxmox.com/debian/pve trixie InRelease
Reading package lists... Done
root@pve-node0:~# apt install numactl -y
Package numactl is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Error: Package 'numactl' has no installation candidate
root@pve-node0:~#

Researching said I needed to add the universe repository...so I tried
Code:
root@pve-node0:~# add-apt-repository universe
-bash: add-apt-repository: command not found
root@pve-node0:~#

Researching this error said I needed to add the software-properties-common module...so i tried

Code:
root@pve-node0:~# apt-get install software-properties-common
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package software-properties-common
root@pve-node0:~#

Researching this said that the software-properties-common turned up
"software-properties-common was removed from Debian 13 (Trixie) in testing."

So is numactl just borked at this point if you dont already have it installed?
 
Hi @mouse51180 , welcome to the forum.

You are mixing Debian (PVE userland) and Ubuntu (universe repo). What happens when you run "apt update" now?

What is in your:
cat /etc/apt/sources.list

ls -al /etc/apt/sources.list.d/
cat /etc/apt/sources.list.d/*


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
  • Like
Reactions: mouse51180 and UdoB
I am new to Linux and Proxmox....so seeing the "non-free firmware"...I thought it was not necessary since this is a non-licensed lab environment im working on before installing a Proxmox in our production environment...reenabling these non-free firmware repositories fixed my issue.

Thanks