podman-desktop-companion VS zfs

Btw #2: For a nice, cross-platform GUI app thing for Docker & Podman here's this one: Podman Desktop Companion.

Podman Desktop Companion (cross-platform, supports Docker too)

Docker in WSL2 too works but with Podman the environment setup may be a little more flexible depending on what you want to achieve on what distro etc. In any case you can use the cross-platform Podman Desktop Companion app to manage your containers via a GUI.

Both Distrobox and Podman can be installed without root access btw and, here's a neat little GUI for managing Podman & Docker containers: Podman Desktop Companion (cross-platform).

No, that's incorrect. Also, there's the unofficial Pods app, and the Podman Desktop Companion.

For a GUI to manage your Podman and/or Docker containers, install the Podman Desktop Companion app (yes, it supports both Podman and Docker). They say that the Windows version can be used to manage the containers running in WSL2 but a more sure way would be to pick the Linux app and to install it in the WSL2 distro your containers are installed & running in.

I'm skeptic how long this will last unless they bring out some cutting-edge innovations. I frankly used and loved Docker Desktop for a long time because it was the easiest way to get going and I believe even k8s is included now which is great for hobbyists and those who just want to get things done. But, I've been annoyed by the UX changes and the push to login to docker hub.

While in 2023, there are most certainly great alternatives that are relatively easy to install from the terminal and get going, I guess there's not yet a definitive replacement that comes with the GUI too. Best I can think of is Podman Desktop Companion[1] but not sure how well this works.

[1]: https://iongion.github.io/podman-desktop-companion/

How does this compare to Podman Desktop Companion? They look very similar - nearly identical - yet clearly two different projects.

Be careful if you use ZFS-on-root, make sure not to snapshot bpool or it will brick your system and require a complete reinstall.

https://github.com/openzfs/zfs/issues/13873

> The only non-junk PCIe3 option that's even advertised here recently is the overpriced WD Red SN700.

Those WD drives seem to have some real issues, at least with ZFS and btrfs. :(

https://github.com/openzfs/zfs/discussions/14793

IMO the "next fs" is just zfs. They somewhat recently merged RAIDZ expansion feature https://github.com/openzfs/zfs/pull/12225 and make regular improvements. If no file system has what you need today, zfs will probably be the first one to have it "tomorrow," imo.

https://github.com/openzfs/zfs/issues/15526#issuecomment-181...

> zpool get all tank | grep bclone

> kc3000 bcloneused 442M

> kc3000 bclonesaved 1.42G

> kc3000 bcloneratio 4.30x

> My understanding is this: If the result is 0 for both bcloneused and bclonesaved then it's safe to say that you don't have silent corruption.

A couple years ago, I had an idea for convincing a filesystem to go faster using 2 compression steps instead of one. I couldn't see why it wouldn't work, and I also couldn't convince myself it should.

It seems to have worked out. [1]

[1] - https://github.com/openzfs/zfs/commit/f375b23c026aec00cc9527...

https://github.com/openzfs/zfs/issues/7631

This is a long-standing issue with zvols which affects overall system stability, and has no real solution as of yet.