File /usr/share/ublue-os/distrobox/pytorch-nvidia.ini does not exist

General
1

Hello community,
I was just following along with the intro docs .
But I get this error when trying to do just distrobox-ml

File /usr/share/ublue-os/distrobox/pytorch-nvidia.ini does not exist.

I believe it might have to do with the latest command I did or atleast I thought that was the reason ;

sudo bootc switch ghcr.io/ublue-os/bluefin:latest

So I thought I had to fix it but this command doesn’t exist ;

sudo bootc switch ghcr.io/ublue-os/bluefin-dx-nvidia:latest

a bit confused. Thank you.

2

It sounds like you’re not up to date, can you paste in rpm-ostree status so we can check? Thanks!

3

Hi j0rge you were right I suppose. I’m just confused because I did the install with bluefin-dx-nvidia … and just following the instructions along .

❯ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:latest
                   Digest: sha256:71b6ca2ef901363aefbb7c18d5b330e35fe204154e5b468d3d03152d69bb396d
                  Version: 39.20231223.0 (2023-12-23T18:08:22Z)
          LayeredPackages: helix micro neovim

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:latest
                   Digest: sha256:71b6ca2ef901363aefbb7c18d5b330e35fe204154e5b468d3d03152d69bb396d
                  Version: 39.20231223.0 (2023-12-23T18:08:22Z)
          LayeredPackages: helix micro neovim

and here are the errors when trying to rebase:

❯ rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:latest
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:latest
Importing: ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:latest (digest: sha256:41babc22f9c6c0ad8107beb83ba54db7046ea04d6c3f7bf5c1af17df09241432)
ostree chunk layers already present: 65
custom layers already present: 2
custom layers needed: 2 (1.4 GB)
Checking out tree 48b2420... done
Enabled rpm-md repositories: copr:copr.fedorainfracloud.org:ublue-os:akmods fedora-cisco-openh264 updates fedora rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates rpmfusion-nonfree updates-archive
Updating metadata for 'updates'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'copr:copr.fedorainfracloud.org:ublue-os:akmods' (cached); generated: 2023-12-09T03:59:38Z solvables: 60
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2023-03-14T10:57:01Z solvables: 4
rpm-md repo 'updates'; generated: 2023-12-24T02:38:58Z solvables: 16786
rpm-md repo 'fedora' (cached); generated: 2023-11-01T00:12:39Z solvables: 70825
rpm-md repo 'rpmfusion-free-updates' (cached); generated: 2023-12-22T13:27:08Z solvables: 108
rpm-md repo 'rpmfusion-free' (cached); generated: 2023-11-04T16:49:08Z solvables: 445
rpm-md repo 'rpmfusion-nonfree-updates' (cached); generated: 2023-12-22T13:50:27Z solvables: 56
rpm-md repo 'rpmfusion-nonfree' (cached); generated: 2023-11-04T17:26:32Z solvables: 208
rpm-md repo 'updates-archive'; generated: 2023-12-25T01:35:16Z solvables: 18828
Resolving dependencies... done
Relabeling... done
Checking out packages... done
error: Checkout binutils-2.40-13.fc39.x86_64: Hardlinking b0/5c0ba45128dbfb28a8089c44e19f93cd0e4531678f017696f69515b916f6c3.file to ld: File exists
4

Try removing your layered packages with rpm-ostree reset, then rebase, then you can add them back. That should unstick it.

5

That did do it , I kept going in loops confused. Many thanks.
Just want to note that it might happen to others but in terms of docs ; I went for a loop amongst 3 sites :

Might be confusing for newcomers (myself included , initially trying to get bearings straight with google searches kind of chaotic.

6

Yeah we still need to move some docs from that site into the forums so we can maintain them better, just haven’t gotten around to it!

1 Like
7

This is the coolest thing I’ve come across for adoption . I know I might not be the target audience (non developer and all) ; but you’ve created something that is accessible. I also feel that its dummy-proof. The entire concept of being able to go backwards without having to do that old chroot / boot usb thing. I’m super appreciative of the work you guys are doing on this.

1 Like