mr-bryn comments

Results 7 comments of


                                            mr-bryn

Check for Tensorflow requirements failing wrongly?

I have a very similar issue running under NC snap - could be related? #1120

Could not execute the Node.js binary. You may need to set the path to a working binary manually.

I am also running Nextcoud snap in an x86_64 VM and have run into exactly the same issue as @Hopp0 I added some debug lines to [lib/Migration/InstallDeps.php](https://github.com/nextcloud/recognize/blob/main/lib/Migration/InstallDeps.php) within the installNodeBinary...

Could not execute the Node.js binary. You may need to set the path to a working binary manually.

@Hopp0 do you have a link to the node version that worked for you so I can test it later?

Could not execute the Node.js binary. You may need to set the path to a working binary manually.

Exactly the same results here trying to use node v20. It works fine from the shell. I opened a shell within the snap environment `snap run --shell nextcloud.php-fpm` When I...

Could not execute the Node.js binary. You may need to set the path to a working binary manually.

> It seems the node project updated their minimum required GLIBC version which is why the pre-built binaries fail on older systems that don't have version 'GLIBC_2.28'. You can check...

Could not execute the Node.js binary. You may need to set the path to a working binary manually.

[I asked the question over on nextcloud snap](https://github.com/nextcloud-snap/nextcloud-snap/issues/2808). Doesn't sound like it will be resolved for a while.

Newer version of glibc to support Recognize WASM mode

> The proper way Does this mean there is an 'improper' way until work to use the new core is done?