Yep the guide modifies fstab
which works.
The KDE Device Auto-Mount
works fine on regular Fedora, so it is probably just incompatible with Atomic/Immutable. I’ll open a bug with KDE
Yep the guide modifies fstab
which works.
The KDE Device Auto-Mount
works fine on regular Fedora, so it is probably just incompatible with Atomic/Immutable. I’ll open a bug with KDE
It’s a SATA connected NTFS HDD. It appears under the Attached Devices
section.
Dioxus desktop and fullstack worked out of the box. Bevy isn’t working because some Nvidia libraries aren’t in the container. I might need to switch to a different ‘GPU enabled’ image.
How did you go with the VPN? I will be looking at that next. I’m using Proton VPN which has an rpm package, but if that doesn’t work I can fallback to manually setting up the WireGuard config.
Are you accessing that through the browser? It might just be bridging the networking in that case.
The executable that I would be running is cargo
(the rust build tool) but I want that inside of a container.
I could cargo build
inside the container and then execute the output binary on the host but then I lose things like hot-reload.
This worked 👍 Thank you I also filed a bug report https://bugs.kde.org/show_bug.cgi?id=485403
The monitor does not display with kscreen-doctor -o
as it’s disconnected.
I will create a bug report.
I’m running uBlue’s AuroraOS. Have been very happy with it so far.