You'd need some sort of translation layer to allow older versions of the Android userland drivers in the container to talk to the modern Android userspace drivers. Or you could write new userspace drivers inside the container that interact directly with the hardware, but this would likely be expensive and insecure. Definitely doable tho, especially for a company as large as Google.
Especially on Pixels, with the generic system image feature (allows for booting generic, non-device-specific android images), if the container is built with the same userland drivers as a generic system image, it might not even need any special effort/attention to run, though iirc GSIs are pretty recent, so you wouldn't be able to run software for anything before like,, Android 12 or 13 probably.
I’m glad my current car is a 2015 Mazda. It’s recent enough to have a touch screen and Bluetooth, but not so recent that it’s got an LTE/5G radio that can phone home and let them sell my driving data to insurance companies or force subscription payments on me. When I get my next car in a decade or so, hopefully I can import a cheap Chinese EV that’s either easy to jailbreak, or doesn’t have any of that bullshit included.