melchor629
commented
2 years ago Hi, you can start with using the DEBUG environment variable. During installation if you use DEBUG=flac:build (or just DEBUG=flac:*) you should get some insights of what is doing internally. But the download is made by prebuild-install (if there is a binary compatible) so, I recommend to also set the npm log level to verbose during the install to see the logs from that package (see https://docs.npmjs.com/cli/v8/using-npm/config). Just to setup it up quickly, defining the environment variable npm_config_loglevel=verbose should work.
On the other hand, don't know how are you building the docker image but as a recommendation, you should only copy the sources and the package.json and package-lock.json into the Dockerfile and then run npm install (and whatever other steps you require). This way you ensure that the environment inside the image is "as pure as it can" (?).
First try getting the logs out and if you find something just post it here. If not, you can put logs here (or in a gist/pastebin/whatever).
Also, which version of the package are you using? (latest I guess, just to confirm) Which is your base image in docker? (node? some debian?)
Happy christmas btw :)
cerbaire
Hello, I created a new docker image of my application and deployed it on my NAS. The container failed to start. After investigation, I found that the problem is when loading flac-bindings.node. I think it is the first time I build my image on a Intel MacOS to deploy in it on my Intel NAS, so maybe the bad version of flac-bindings.node is downloaded when creating the docker image. So I uninstalled and reinstalled flac-bindings package in the container, but is does not solve the problem. I don't find trace of what version of the binary is downloaded when running npm install. I tried with node 10, 12, 14 and 16 without success.
Any clue on why I can't get the good version of the binary for my NAS ? Or how I can solve the problem ? Thanks for your support.