This message was deleted.
# rancher-desktop
a
This message was deleted.
q
we're seeing java throw a
Function not implemented
when someone calls
inotifyInit
or something
i
I think this issue is about what you described https://github.com/rancher-sandbox/rancher-desktop/issues/1979
q
I saw that, it doesn't seem right. We're not asking for inotify events to come from the host. We're just asking for inotify to pretend to be available
We don't need inotify to ever fire events, it's just that these java modules die because they can't get inotify to initialize -- even though for a static build there's really no reason to notify about file system changes since it's just a build agent building a package once.
f
I think this is the same as In docker desktop preview, the inotify function fails on a container with platform set to linux/amd64. · Issue #5321 · docker/for-mac which says the only workaround is to use arm64 images instead.
It may be possible that this will work when using the Virtualization.Framework instead of QEMU, but I don't know.
q
Surely there's some way to just let it register and not do anything?
I don't want events I just want it to let the stupid thing ask for them
f
Either way, VF support is still under construction
Patch your app to use a mock for the function, if possible
Otherwise, it seems like a limitation of the emulator
Beyond that, I hope we soon have VF support (will require Ventura though), which should in general provide much better performance (and allow us to use Rosetta2 inside the VM to run amd64 binaries, instead of qemu-static).
q
My app is
sbt
on top of the linked
swoval
on top of the general Java Runtime. I personally feel that each of Java, swoval and sbt are buggy, but I don't expect any of them to be particularly cooperative in reasonable time. I wonder if there's a syscall wrapper thing available that could just lie to the jvm.
261 Views