You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using libxml through samlify and I have some problem when using my app in a Docker Alpine container (base on the official node one):
> [email protected] start /opt/app
> node -r make-promises-safe lib/index.js
/opt/app/node_modules/bindings/bindings.js:88
throw e
^
Error: Error loading shared library xmljs.node: No such file or directory (needed by /opt/app/node_modules/libxml-xsd/build/Release/node-libxml-xsd.node)
at Object.Module._extensions..node (module.js:689:18)
at Module.load (module.js:573:32)
at tryModuleLoad (module.js:513:12)
at Function.Module._load (module.js:505:3)
at Module.require (module.js:604:17)
at require (internal/module.js:11:18)
at bindings (/opt/app/node_modules/bindings/bindings.js:81:44)
at Object.<anonymous> (/opt/app/node_modules/libxml-xsd/index.js:8:34)
at Module._compile (module.js:660:30)
at Object.Module._extensions..js (module.js:671:10)
I tried to build and rebuild with gyp, I checked the content of node_modules/libxmljs-mt/build/Release/, xmljs.node is there (in obj.target too) and it works perfectly outside of Docker.
Do you have any clues on why this happens once in a container?
Thank you
The text was updated successfully, but these errors were encountered:
Unfortunately I don't have the time to actively maintain this project and I don't remember encountering this problem. However I accept pull requests, in case you find a fix...
Hello,
I'm using libxml through samlify and I have some problem when using my app in a Docker Alpine container (base on the official node one):
I tried to build and rebuild with gyp, I checked the content of
node_modules/libxmljs-mt/build/Release/
,xmljs.node
is there (inobj.target
too) and it works perfectly outside of Docker.Do you have any clues on why this happens once in a container?
Thank you
The text was updated successfully, but these errors were encountered: