nixpkgs VS waydroid

https://github.com/nixos-bsd/nixbsd This is a very cool project that I hope will get upstreamed into NixOS proper, eventually.

I always thought InitWare would be good for that. See https://github.com/NixOS/nixpkgs/issues/26850 --- we've been discussing this before NixBSD existed, even!

If you are currently involved in managing packages for a Linux distribution, then you might want to use the instructions outlined in the GitHub repo to help you build packages for your distributions. My colleague James Ward has recently done this for NixOS (you can see his PR here)

You can do this with vanilla Firefox using policies.json[1]. Check out `DisableAppUpdate` attribute.

If you're using Firefox from nixpkgs this is already disabled by default[2].

[1]: https://support.mozilla.org/en-US/kb/customizing-firefox-usi...

[2]: https://github.com/NixOS/nixpkgs/blob/nixos-24.11/pkgs/appli...

Ah, this is awesome! I currently run k3s on a decently spec-ed NixOS rig. I tried getting k3s to recognize my Nvidia GPU but was unsuccessful. I even used the small guide for getting GPU in k3s to work in nixpkgs[0], but without success.

For now I’m just using Docker’s Nvidia container runtime for containers that need GPU acceleration.

Will likely spend more time digging into your findings — hoping it results in me finding a solution to my setup!

[0] https://github.com/NixOS/nixpkgs/blob/master/pkgs/applicatio...

- Method 1: doesn't really improve layer caching, but it provides a familiar way (via Dockerfile) to use Nix packages. As with any Dockerfile, the creator is in charge of creating layers and making sure those layers are as small (cleaning cache, ...).

- Method 2: Nix language is used to describe (in a declarative way) what the end image should look like. Layers are then calculated based on the dependency tree (or as Nix calls it, dependency closure). The algorithm that creates layers[1] makes sure that there is higher likelihood of cache hits without the user needing to worry about layers, but you can even roll-up your own algorithm that fits your project better.

- Method 3: Using Flox you would get sort of both. An easy way to configure the final docker image via toml configuration and using Method 2 under the hood.

There are other ways how to improve caching efficiency, but those are very use case specific (eg. big "builder" images) and would probably require a completely separate blog post.

[1] https://github.com/NixOS/nixpkgs/blob/63f0da03a3b2c323ea924b...

I spent a while messing around with https://github.com/ansiwave/nimwave, which I enjoyed but I haven't gotten very far. Though I've been avoiding the front end for so long, I don't know what reasonable feels like in that space anyway.

My Nim journey was stalled by this bug in its nix toolchain: https://github.com/NixOS/nixpkgs/issues/308593. I guess that's the price we pay for straying from the beaten path.

The build will actually fail if Gixy finds any issues.

[1]: https://github.com/NixOS/nixpkgs/blob/nixos-24.11/nixos/modu...

> You also couldn't feasibly do that for derivations that actually build packages, [..] you would have to update all of the affected hashes.

You can actually, changes to stdenv are possible and "just" a lot of work. You will regularly see them between releases or on unstable and they cause mass rebuilds. This doesn't just affect a compiler but also all stdenv tooling as these changes tend to cause rebuilds across nixpkgs. This would be verifiable but it obviously multiples the amount of compute spent.

Hint: If you look at PRs for nixpkgs you will notice labels indicating the required amounts of rebuilds, e. G., darwin:1-10. See for example https://github.com/NixOS/nixpkgs/pull/377186 with the darwin:5001+ label.

In theory you have the likes of the PinePhone where you can run a full Linux kernel [1]. You could then use something like Waydroid to run Android apps [2].

I think the biggest concern is that many of the important apps are anti-emulation, for example banking apps and authentication apps.

[1] https://pine64.org/devices/pinephone_pro/

[2] https://waydro.id/

I think it does, to the point where plugging in USB devices while Android has focus accidentally captures the USB device: https://github.com/waydroid/waydroid/issues/778

If not, it's just a Linux container, so with some udev rules you should be able to make it work regardless.

Android on the desktop works very well on Wayland with Waydroid and it even supports Google Play store. https://waydro.id/

Great running apps not available on Linux with a touchscreen PC. It only seems to run Android apps compiled for x86, but it is very fast.

There are practical use cases, and it is very usable. I haven’t tried it on WSL2, but it seems like a practical approach without reliance on Microsoft.

There's a piece of software called Waydroid[1] that allows you to run Android applications on GNU/Linux platforms - including the PinePhone. Sxmo, despite its name, can run Wayland instead of X and therefore supports Waydroid.

Personally, I haven't managed to get Waydroid to work, a task hindered due to some massive initial downloads which are required to set it up. However, I haven't tried particular hard, and there are videos online by those more successful than me[2].

[1]: https://waydro.id/

[2]: https://tilvids.com/w/2b2f3a24-ae23-458e-a0fd-2f24a185a11b

I thought it was uncharacteristic of to see a service like this offered by a large tech company, and wanted to share.

Found whilst installing Waydroid: https://waydro.id/

Check out the Waydroid application.

I have setup an Arch linux server on my old pc. i mainly use it for plex, transmission, docker etc and it works pretty well! I wanted to install Waydroid https://waydro.id/ on that server. Is there a way that I can view waydroid using a VNC viewer on my laptop on the same network? is it possible or would I have to install a GUI like xfce before installing waydroid to view the same on tigervnc or some other VNC viewer? Thanks & regards.