-
Notifications
You must be signed in to change notification settings - Fork 548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add gcompat for the recognize app #1569
Conversation
Signed-off-by: Simon L <szaimen@e.mail.de>
@marcelklehr I read that gcompat is required for the recognize app to work. Is this correct? :) |
Hi, this is based on my gist https://gist.github.com/thomasverelst/60403f22e7a9f5200b0dc43615c54720 |
Huh, I never read that anywhere. I've been running it fine inside docker on an x86_64 machine (until the setup destroyed itself, but that's another story...). EDIT: Ah, you mean for the alpine package, yeah, glibc is necessary if you don't want to run in WASM mode |
This is now released with v4.0.1 Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel |
Hello, With the actual beta tag from docker hub, I still have the issue mentioned here : nextcloud/recognize#604 Do you have any idea how to debug it? Thanks ! |
@erwanlpfr Hello! Can you try running |
Hmm, I waited one day and it seems to work. Thanks for your reply! |
Great! I'm happy it works now :) |
@marcelklehr For me recognize still doesn't work in nextcloud-aio container, gcompat doesn't solve the issue with libtensorflow not beeing compatible with Alpine/musl. The following command never finishes. That explains the loading icon of recognize described here: nextcloud/recognize#609
If I install Alpine's musl version of nodejs (v16.17.1) via apk, the
without gcompat, libtensorflow complains about the missing glibc library:
|
In that case I'm out of ideas. |
@fabianbees thanks for testing! Can you check if adding |
That I have also tested already, for me it didn't make any difference, unfortunately still the same issue. Maybe the only viable long term solution for enabling compatibility with recognize would be to move this container back to debian userspace which uses glibc natively. |
No, moving back to debian is not an option for AIO. So we need to find a way to make it work with alpine linux. |
What I wonder: wasnt recognize already running in wasm mode on alpine linux in the past? Why is it not running at all anymore? Should we remove gcompat again? |
Wow, is this the final answer? tensorflow/tfjs#1425 I thought recognize was able to work in wasm mode at some point? |
I believe it still works in WASM mode. WIth gcompat the check whether libtensorflow can be loaded just never ends. WIthout gcompat it simply fails. |
I see. Then removing gcompat again probably makes sense since it at least finishes the test then and allows to enable the wasm mode. |
Will be done in #1816 |
This is now released with v4.3.0 Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel |
I think the beta update (Nextcloud AIO v4.3.1) broke my recognize (reinstalled v3.4.0) (WASM toggle enabled in Recognize settings)
In logs:
It used to work before (in WASM mode on ARM), so it seems that some setups require gcompat (luckily its easy to add manually). I hope I'm not looking at this in the wrong way, just reporting what I see :-) |
There seems to be no way to make it work for everyone so we removed gcompat again (as it breaks recognize on other instances). But if you need it you can add it back as you did 👍 |
Looks like this should fix the requirement on gcompat for arm64 in a future update: nextcloud/recognize@30602dc |
It is needed for the recognize app IIRC.
Signed-off-by: Simon L szaimen@e.mail.de