4 Feb
2025
4 Feb
'25
12:15 p.m.
Fwiw there was some previous attempts before (see !535 and !360) and as I understand it's mostly blocked by !359, which is necessary to store the mmdevapi property correctly. The issue is that we need to change the format of the properties in the registry and it would break existing prefix if not done properly.
Other than that, the changes would probably need to be split into finer grained changes. I'm also not sure we want to expose the sysfs path outside of the unix libraries. It's very specific to the linux backend, and even more to the udev backend. I would instead try to make both unix-side code generate a similar stable container id from whatever information they can get, and get that container id exposed instead.