vm-bhyve VS matchhostfsowner

https://github.com/churchers/vm-bhyve/wiki/UEFI-Graphics-(VN...

Other than that, I use bhyve on my laptop daily since around 2015-2016. It was somewhat painful at first. I had to bake a CD key into Windows ISO for headless install but now VNC support exists and it's easy to output any graphical installer via VNC.

bhyve doesn't offer API and has not the most user-friendly interface (vm-bhyve[1] for the rescue!) but overall, I couldn't be happier with its - typical for FreeBSD - _set-and-forget_ stability.

[1] https://github.com/churchers/vm-bhyve

I am using FreeBSD in the workstation, I have both intel and realtek, and the main network uses the LAN interface, but I need the VLAN 20 to assign IPs from that range to some VMs (https://github.com/churchers/vm-bhyve/wiki/Virtual-Switches)

I want to assign IPs from VLAN 20 172.16.1.0/24 to VMs (https://github.com/churchers/vm-bhyve/wiki/Virtual-Switches) running on a host where main IP 192.168.1.10 is on the LAN network (no VLAN 20) this is the setup:

Sample config: https://github.com/churchers/vm-bhyve/blob/master/sample-tem...

I use Jails to run applications like Postgres, Redis, Python api in an isolated environment. Jails is native FreeBSD, but isolated.

Of what is properly supported, works beautifully and I have to say vm-bhyve is a joy to use. Everything is very cohesive and solid as a whole; I recommend it for servers but for GPU passthrough, only if you like a challenge.

I recommend to look into some third-party tooling to manage VMs. I prefer vm-bhyve, https://github.com/churchers/vm-bhyve

I was thinking opnsense + https://github.com/churchers/vm-bhyve to run a debian instance, which can then run everything in docker containers. It's inception but better utilization of all the services.

Perhaps it would! But the userbase is definitely what finally got me into FreeBSD. The fact that hobbyists were contributing such excellent cli tools as `iocage` [0] and `vm-bhyve` [1] really is what got me over my fears.

[0] https://iocage.io/

[1] https://github.com/churchers/vm-bhyve

I wrote a portable solution for the user ID mapping problem: https://github.com/FooBarWidget/matchhostfsowner

I'm at the verge of releasing version 1.0 of MatchHostFsOwner, a solution for the Docker filesystem owner matching problem. MatchHostFsOwner is my first serious Rust project. It's an entrypoint program to be used in Docker containers. Rust's error handling idioms force me to take all possible error conditions seriously, while also encouraging me to have proper error messages for each error condition. I use rust-musl-builder to generate statically-linked Linux binaries that work on all Linux distros.

I'm working on a solution based on strategy 1 (matching the container's UID/GID with the host's). This solution already works, and I've already deployed it in a few of my own projects, but isn't very well-documented yet. I'm also working on more automated tests to guarantee that it's rock-solid. Would you be interested in testing it and giving feedback once it's in a more ready state?