container issue on launch

[xfouloux]

Hey guys,

i just pulled the container and i've this on logs when it starts

npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/node/cloudproxy/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/node/cloudproxy/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2020-12-14T01_58_45_963Z-debug.log
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/node/cloudproxy/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/node/cloudproxy/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2020-12-14T01_58_58_364Z-debug.log

Something went wrong with the latest build i guess

[xfouloux]

@abeloin don't mind me =) ! i had to fully recreate the container, because i had some env values from noahcardozza container, i guess paths for NPM and stuff

Might be a good thing to indicate people they need to recreate the container fully in case of issue like this ^^

[ngosang]

You to use pre-built Docker images if you want to => https://github.com/FlareSolverr/FlareSolverr#docker