Bhyve vs Podman for linux

I've been running Linux (mostly Arch) for ca 9 years and had Affinity Studio (only available for Windows), for photo editing up and running on Arch using Wine. I switched for FreeBSD (15p7) are few weeks ago and, basically, have everything that I was using before up and working. I would like to try and get Affinity work, though not a deal breaking if I can't. So the question is would I be better off trying to use Bhyve or Podman running docker ? It would have to to be a Linux container (prefer Arch, but i guess it really doesn't matter), with graphics, and able to use Wine).
Any thoughts, suggestions, etc.

Thanks
 
Why not wine? It's on ports. And it's better integrated with the graphics stack of FreeBSD for windows programs.

By default the linux compatibility layer (rocky linux 9) will only support OpenGL (with patches/hack vulkan works, cuda maybe).

Podman requires root and has still some hard edges. VMs or jails I have little experience with getting windows working (virtualbox should also be an option though).
 
I'll maybe try Wine in a Bhyve container running FreeBSD15 as a test to make sure I don't pouch my real system.
The problem with Affinity on Linux, is not only does it require Wine (it's a Windows and Mac program only) is that some of the Wine DLL's require special patching. There are several Linux scripts to install Affinity on Linux that, mostly work.
 
I got A Linux (Arch Linux) Bhyve container up and running and it seems to be working as expected.
I also got Affinity installed in said container using one of the special Linux scripts that handle the mods to some of the DLLs.

What I need now, and I've been trying to search for way, is to allow the Bhyve container to have access to my actual FreeBSD drives so that I can move my photos in and out of the container.
I'm sure it's something that I missed in the setup of Bhyve (I've been using VM-Bhyve)
 
One way--not necessarily the best, but for my circumstances useful--is to put the bhyve VM on the same subnet. I use bhyve-vm, and create a public switch. Then, when I create a new VM, it is on the same subnet as the host machine, so I can just ssh to it, rsync to it, or whatever.
 
Back
Top