I’m working on my transition plan away from Windows and testing out various things in VMs as I do so, and one big hurdle is making sure the VPN client my work requires can connect. Bazzite is my target distro (primarily gaming, work less frequently), though other more traditionally structured ones like Pop!_OS and Garuda are possibilities.

I’m currently trying and failing to get the VPN client working in a distrobox (throws an error during connection saying PPP isn’t installed or supported by the kernel). However, I can successfully get the VPN connected if I overlay the client and its dependencies via rpm-ostree install, but I read somewhere that Bazzite’s philosophy is to use rpm-ostree as sparingly as possible for installing software to preserve as much containerization as possible.

Since I can get it working outside of a container, am I overthinking it? Should I just accept that this might be one of the “sparing” cases? Is Bazzite perhaps a poor fit for my use case? I’ve been trying to make sense of this guide, but I’m having trouble understanding how to apply it to my situation, since I’m not that familiar with Docker or Podman.

  • Telorand@reddthat.comOP
    1·
    6 months ago

    Sorry I didn’t get back sooner, but I made some progress.

    What do you mean with “work in progress”?

    Their words (second video, I think), and more in reference to how they are still working out how they haven’t yet covered all of the use cases (like maybe my needs can’t currently be met by rpm-ostree or bootc). rpm-ostree has functional limitations, and bootc is still being developed. Obviously, both are still useable and useful, and Universal Blue has been using them for quite a while. I may have been reading too much into it with the “depreciation” comment.

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

    It can’t work on its own. Running with sh or making it executable runs the script, but it fails when it tries to write its icon and .desktop entry to /usr (it also doesn’t take an --appimage-extract argument). You can use sudo rpm-ostree usroverlay to create a temporary FS overlay for /usr, but it’s wiped on the next boot. Still, that allowed the installation to complete.

    I discovered that it’s installing all of the necessary components to /opt, and they remain functional. I was able to manually run the daemon script required and get a WireGuard tunnel established in the client.

    Now, I’m trying to get a .service module to work so it can run automatically as root on a reboot with systemd. So far, it’s giving me a 126 exit code, so I still haven’t figured out how to escalate its privileges automatically, but this is the most progress I’ve made to date.