WSA-Magisk VS distrobox

And/but one may still prefer to build his own versions locally via MagiskOnWSALocal. And in the case of the WSA Preview builds which this project can't access on it's own*, MustardChef/WSAPackages shares these too.

It isn't. It's essentially rooting and flashing gapps onto the WSA "ROM" https://github.com/LSPosed/MagiskOnWSALocal

But a more trouble-free way is to use MindTheGapps by repacking your own WSA via LSPosed/MagiskOnWSALocal.

WSA: 2303.40000.3.0 (LSPosed/MagiskOnWSALocal with MindTheGapps, Magisk-delta)

So, stick to LSPosed/MagiskOnWSALocal and build your own WSA with GApps etc with it's easy to use script. You can use WSL2 to make these WSA builds (as in, just go install Ubuntu from MS Store or something). No need to trust someone's personal project.

I was reading the linked repo in step 2 <https://github.com/LSPosed/MagiskOnWSALocal#magisk-on-wsa-wi...> and saw this message, which seems like utter nonsense:

> For fork developers: Please don't build using GitHub Actions, as GitHub will count your forked GitHub Actions usage against this upstream repository, which may cause this upstream repository gets disabled by GitHub staff like MagiskOnWSA because of numerous forks building GitHub Actions, and counting the forks' Action usage against this upstream repository.

is that even remotely true?

If there's any "disabled by GitHub staff" going on, it's likely due to DMCA nonsense, not due to forks having their GitHub Actions billed against the upstream repo. Related to that, I'm surprised to see the submitted repo distribute icu.dll and winhttp.dll, versus telling interested parties to extract them out of the Win11 ISO. I bet Microsoft won't bother striking the repo over to random dlls but why roll the dice?

Use this to rule Android from Windows (btw).

Anyway, if you need to install & run the Android apps & games that rely on Google Play Games, do give this project a try: https://github.com/LSPosed/MagiskOnWSALocal. It's likely that you'll need to hide certain stuff from these apps/games btw and the official Magisk won't help you much (if any) in that case so ask again if your thing complains about that for an up to date answer by then (but then again, you're talking about PUBGay of all games so you may fail to achieve what you want anyway).

That seems more like Distrobox to me(?) https://distrobox.it/

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

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)

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_...

https://news.ycombinator.com/item?id=38505448 ... https://github.com/89luca89/distrobox/blob/main/docs/useful_...

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

For such cases you might use something like this: https://github.com/89luca89/distrobox

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).

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