If I understand correctly, it just wraps an existing Linux driver in a container. You can hardly call that writing a driver.

Would calling it a "driver adapter" fit more accurately .. ?

I don't think so, no. It does not appear to be functioning as an OSX device driver. It's just hosting a network print server in docker.

	▲	kuberwastaken an hour ago \| parent \| next [-]
		It works with Cmd + P https://x.com/kuberwastaken/status/2089961185047437729
	▲	happyPersonR 14 hours ago \| parent \| prev [-]
		Tbh I actually like this even more than writing a driver … Makes it so if there’s an issue I don’t get a kernel panic Maybe it could write something CUPS compliant though ?

Why not call it a containerized driver?