Aqler , 4 days ago (edited 4 days ago)

Yo OP, this is me @poki from another account. I had intended to leave the Lemmyverse for a while, but had to come back earlier than intended when I read your comment 😅.

So, without further a due.

Okay, I appreciate the links. I’ve had a chance to go over both, and I think I get the gist:

Thank you for your time!

• rpm-ostree is a work in progress, and it will be depreciated and replaced with bootc + dnf

What do you mean with “work in progress”? You’ve been using it relatively often in this thread (and IIRC even in others) when talking about Fedora Atomic and/or uBlue and its technologies. Like, do you consider dnf to be work in progress because dnf5 is around the corner?

I don’t recall any mention of deprecating rpm-ostree, though I might be wrong. But, yeah; it will definitely lose focus in favor of bootc + dnf.

For example, I have a VPN client that is installed via a .run script, so it doesn’t work with ostree. If I wanted to apply this software to my system, I’d have to create a bootable container, then rebase to that.

I’m not actually sure if it works out just like that as of right now. Creating your own image or bootable container is definitely a powerful tool that can help bypass some imposed limits; like e.g. populating files in /usr or baking in (current) rpm-ostree actions -some of which actually wouldn’t work otherwise (as of right now)- directly into the image. Finally, it allows one to move from an imperative to a declarative system. However, I’m not aware if it enables one to bake-in the installation of .run files. My only experience with .run files myself was with Davinci Resolve, but that’s notoriously difficult to install regardless. Thankfully, it’s a popular piece of software and thus avenues have been created by which one could install it on Fedora Atomic and related projects.

So, in short, I don’t see how creating your own bootable container would help you to bypass this.

But my goal isn’t to create a new image, just to apply transient packages to the base Bazzite image

Exactly.

If I made a bootable container(file), would that derived image fall out of sync with the parent Bazzite project?

If you achieve it through legit means (i.e. uBlue’s own documentation on this or through a sister project called BlueBuild), then no.

Would I have to manually build a new container and rebase each time I wanted to check for updates?

By either of the two earlier mentioned means, the building is done automatically (on a daily basis) by GitHub. Furthermore, when you update, you just receive the latest image from your own GitHub repository in which your own image resides. Updates continue to be done automatically in the background, so you won’t even notice. Finally, if it wasn’t clear yet, you only have to rebase once.

I feel like I’m on the cusp of seeing the big picture, but I’m not quite getting it, and maybe that’s because I haven’t worked at all with services like Podman and Docker.

That’s fine. Please feel free to inquire if you so desire!

---

Alright, having said all of that, let’s get to the crux!

So, did you try the following methods when installing the .run file? If so, how did it go?

• Simply double press or right-click then install (of course, after applying chmod +x).
• Within a terminal with ./<name of .run file>.run
• Within a terminal with ./<name of .run file>.run --appimage-extract and then interacting with the AppImage.

If all of the above have absolutely failed, I only see three ways going forward:

• Creating your own Flatpak 😅.
• (OR) Taking this to COPR 😅.
• (OR) Succumb to Toolbx/Distrobox 😅. Like have you tried running the .run file within Toolbx/Distrobox? If so, how did it go?

---

EDIT: 😅. I had hoped you’d return with a reply soon~ish. But alas… Uhmm…, I’ll be off for a couple of days and will return only next week. Just wanted to let you know*. FYI, I’ll probs return with (yet) another account.