Standard update failing due to disk space.

I'm trying to update my system and even after a
ujust clean-system
ujust clean-system
it's still not working. Error: "At least 1MB more space needed on the /usr/share/doc/libva-nvidia-driver filesystem". I have plenty of space but just seems like cache is full? Usually on a Fedora system a
dnf clean packages
dnf clean packages
does the trick but not quite sure what to do to update my system here.
Solution:
GitHub
distrobox/docs/usage/distrobox-assemble.md at main · 89luca89/distr...
Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available...
Jump to solution
8 Replies
HikariKnight
HikariKnight7d ago
rpm-ostree status
df -h
rpm-ostree status
df -h
Pine
PineOP7d ago
bazzite@bazzite:~$ rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia-open:stable
Digest: sha256:325d7ca9b5774caf6a316de88356cfa4b73f867a664aed205c1548c09d15b785
Version: 41.20241125 (2024-11-26T03:48:30Z)

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia-open:stable
Digest: sha256:5c4308757f7cbe94d1a52dcd3f6ed15f1a5c483c712c299c5d3f435bfdce0fc8
Version: 41.20241118.2 (2024-11-19T02:55:29Z)
bazzite@bazzite:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p3 476G 110G 364G 24% /sysroot
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 7.8G 93M 7.7G 2% /dev/shm
efivarfs 184K 145K 35K 81% /sys/firmware/efi/efivars
tmpfs 3.1G 2.3M 3.1G 1% /run
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-network-generator.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-udev-load-credentials.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-sysctl.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev.service
tmpfs 7.8G 10M 7.8G 1% /tmp
/dev/nvme0n1p3 476G 110G 364G 24% /var
/dev/nvme0n1p2 974M 417M 490M 46% /boot
/dev/nvme0n1p3 476G 110G 364G 24% /var/home
/dev/nvme0n1p1 599M 13M 587M 3% /boot/efi
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-vconsole-setup.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service
tmpfs 1.6G 336K 1.6G 1% /run/user/1000
bazzite@bazzite:~$ rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia-open:stable
Digest: sha256:325d7ca9b5774caf6a316de88356cfa4b73f867a664aed205c1548c09d15b785
Version: 41.20241125 (2024-11-26T03:48:30Z)

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia-open:stable
Digest: sha256:5c4308757f7cbe94d1a52dcd3f6ed15f1a5c483c712c299c5d3f435bfdce0fc8
Version: 41.20241118.2 (2024-11-19T02:55:29Z)
bazzite@bazzite:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p3 476G 110G 364G 24% /sysroot
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 7.8G 93M 7.7G 2% /dev/shm
efivarfs 184K 145K 35K 81% /sys/firmware/efi/efivars
tmpfs 3.1G 2.3M 3.1G 1% /run
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-network-generator.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-udev-load-credentials.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-sysctl.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev.service
tmpfs 7.8G 10M 7.8G 1% /tmp
/dev/nvme0n1p3 476G 110G 364G 24% /var
/dev/nvme0n1p2 974M 417M 490M 46% /boot
/dev/nvme0n1p3 476G 110G 364G 24% /var/home
/dev/nvme0n1p1 599M 13M 587M 3% /boot/efi
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-vconsole-setup.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service
tmpfs 1.6G 336K 1.6G 1% /run/user/1000
This is also not my first time updating this system. 🤔
HikariKnight
HikariKnight7d ago
im guessing its just a distrobox failing to update try rpm-ostree update
Pine
PineOP7d ago
Ahhh I see so distrobox failing is normal?
HikariKnight
HikariKnight7d ago
depends on the distrobox container, arch is prone to fail if thats the case we just recommend re-making the distrobox container and if you have a distrobox you use where you just install packages from the main repo only, you can make a manifest and re-assemble that distrobox without having to manually reinstall everything inside the box
Solution
HikariKnight
HikariKnight7d ago
GitHub
distrobox/docs/usage/distrobox-assemble.md at main · 89luca89/distr...
Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available...
Pine
PineOP7d ago
Nice! okay it's gnome but i'm guessing its the same steps
HikariKnight
HikariKnight7d ago
if you make multiple boxes in 1 manifest file you can use our ujust wrapper for distrobox assemble to get a nice list to select what to recreate ujust assemble prompt create /path/to/file.ini doesnt matter, distrobox is cli, gui is boxbuddy and its on both bazzite kde and gnome
Want results from more Discord servers?
Add your server