silverblue-akmods-keys
distrobox
silverblue-akmods-keys | distrobox | |
---|---|---|
8 | 403 | |
64 | 9,026 | |
- | - | |
2.7 | 9.6 | |
7 months ago | 6 days ago | |
Shell | Shell | |
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
silverblue-akmods-keys
-
Fedora Atomic Desktops
I'm using Silverblue 39 for about 2 month coming from NixOS Unstable. It's working very well for me. I have some packages layered like Nvidia and fish shell and https://github.com/CheariX/silverblue-akmods-keys for AKMODS modules work with secure boot. Things like neovim, pyright, helix, starship, LSPs and CLI applications I install with brew (brew.sh). For desktop things I use Flatpak.
I had a problem with some Flatpak applications (like Steam and Discord) and brew because brew puts its folder in the $PATH before the default ones (/usr/bin ...) and those Flatpak applications tried to use SSL keys from brew instead of the system ones. I just changed the order of the $PATH to make brew bin path to be after ther system ones.
For VSCode I'm not using the Flatpak I'm using the tarball one I just extract in ~/applications and symlink the code binary in the ~/.local/bin. It's working well, I don't have problem with VSCode not executing LSPs and lint things. The only problem is VSCode from tarball cannot updates itself, so I need to download the newer version and extract to ~/applications. There is this VSCode CLI version (https://code.visualstudio.com/docs/?dv=linux64cli) but I was not able to make it use the wayland backend.
-
The New Big Picture Mode Does not Seem to Work Well with Nvidia GPUs on Linux clients
rpm-ostree install --apply-live rpmdevtools akmods sudo kmodgenca sudo mokutil --import /etc/pki/akmods/certs/public_key.der git clone https://github.com/CheariX/silverblue-akmods-keys cd silverblue-akmods-keys sudo bash setup.sh rpm-ostree install akmods-keys-0.0.2-8.fc$(rpm -E %fedora).noarch.rpm
- Hello dear community, I have another question about Fedora Silverblue, Nvidea and Secure Boot. Is it possible to install and use the proprietary driver with active Secure Boot?
-
Do NVIDIA drivers still need to be signed manually ?
On workstation, no. On Silverblue, yes. There is a package on Github that will help you if you are on Silverblue. Link here: silverblue-akmods-keys
-
Nobara Linux
It works, but only with a hack where you manually have to overlay a self build package that provides the akmod keys.
-
Fedora is way better than Ubuntu
Unfortunately I can't test it, as this feature is currently still broken (workaround) on Kinoite/Silverblue and Silverblue is the only version of Fedora I use.
-
Tip: if you're not on F37 yet, you can check your security level using the 'fwupdmgr security' command
Kinoite and Silverblue have problems signing akmods, though https://github.com/CheariX/silverblue-akmods-keys is a completely functional workaround. Non-rpm-ostree variants of fedora should work according to what I have seen online.
- Doing a complete reinstall - options overview, questions and suggestions?
distrobox
-
Show HN: Convert your Containerfile to a bootable OS
That seems more like Distrobox to me(?) https://distrobox.it/
-
Windows 11 now comes with its own adware
Regarding the stability issue on a dev machine - you may be interested in playing with one of the immutable-os distros, such as SilverBlue (fedora based).
The high-level take-away is you can't break your actual OS since it's root filesystem is read-only, and you use "pet" containers (on docker, podman, whatever) to do your work in. Applications are either sandboxed via Flatpak, or installed/run inside your pet containers. If your pet container dies, you cry about it for a moment, and when you're ready you get a new one - your actual os and other containers remain unaffected.
I use distrobox[1] to create/run the pet containers.
[1] https://github.com/89luca89/distrobox
-
Tools for Linux Distro Hoppers
Distrobox is a tool that enables us to try Linux distro CLI, including their package manager. This requires a containerization tool (e.g., Docker). In Windows, this can be achieved using WSL (Windows Subsystem for Linux)
- Distrobox: Use any Linux distribution inside your terminal
-
Fedora Atomic Desktops
I use containerized versions of things, ubuntu and chainguard images mostly.
You can always create containers with init if that's how you want to do that though. Some distros publish images that come that way: https://github.com/89luca89/distrobox/blob/main/docs/useful_...
-
Raspberry Pi is manufacturing 70K Raspberry Pi 5s per week
https://news.ycombinator.com/item?id=38505448 ... https://github.com/89luca89/distrobox/blob/main/docs/useful_...
-
Operating System?
Yes, you can do that but I've seen others use something like distrobox to run linux inside of SteamOS: https://github.com/89luca89/distrobox/blob/main/docs/posts/steamdeck_guide.md
-
How much will I screw up my system after installing Merkuro Calendar (KDE Akonadi application), formerly called Kalendar, on GNOME?
For such cases you might use something like this: https://github.com/89luca89/distrobox
-
Battery consumption of using remote development with WSL2?
Btw #3: Depending on what the user is trying to accomplish, e.g. maybe to make WSL(2) itself more of a "subsystem" than a "container engine", using something like Distrobox or nsbox.dev can be a good idea (along with Docker or Podman in Distrobox's case; the other one uses systemd-nspawn).
-
Cannot run containers with Distrobox
1. Find here in "Containers Distros" section the distro image that you want to install ("Toolbox" versions are better because they are configured for Distrobox) and get it URL: https://distrobox.it/compatibility/#containers-distros 2. Use that URL to create Distrobox: distrobox create -i registry.fedoraproject.org/fedora-toolbox:39 -n fedora_1_39 3. Enter Distrobox fedora_1_39: distrobox enter fedora_1_39 4. You are already in Distrobox console. Look at the name in console, it should be include the container name. 5. To exit Distrobox: exit 6. If you run: distrobox list you will see all distroboxes on the system. You will also see that distrobox that we exited is still running. 7. To stop distrobox use commands: distrobox stop fedora_1_39
What are some alternatives?
fwupd - A system daemon to allow session software to update firmware
toolbox - Tool for interactive command line environments on Linux
issue-tracker - Fedora Silverblue issue tracker
wsl-distrod - Distrod is a meta-distro for WSL 2 which installs Ubuntu, Arch, Debian, Gentoo, etc. with systemd in a minute for you. Distrod also has built-in auto-start feature on Windows startup and port forwarding ability.
Visual Studio Code - Public documentation for Visual Studio Code
docker-android - Android in docker solution with noVNC supported and video recording
flatpak - Linux application sandboxing and distribution framework
rustdesk - An open-source remote desktop, and alternative to TeamViewer.
toolbox-vscode - Toolbox Visual Studio Code integration
nix - Nix, the purely functional package manager
toolbox - The Docker Toolbox
vscode-dev-containers - NOTE: Most of the contents of this repository have been migrated to the new devcontainers GitHub org (https://github.com/devcontainers). See https://github.com/devcontainers/template-starter and https://github.com/devcontainers/feature-starter for information on creating your own!