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
Hello, as far as I can see your example should work out of the box, but it doesn't.
What did I do?
I put example.js to the root directory, made a subdirectory output from there and started your instruction:
# echo example.js | docker run -i --rm --security-opt seccomp=$HOME/chrome.json \
> --mount type=bind,source="$(pwd)"/output,target=/output \
> --name puppeteer-headless \
> justinribeiro/puppeteer-headless \
> node -e "`cat $_`"
[eval]:1
example.js
^
ReferenceError: example is not defined
at [eval]:1:1
at ContextifyScript.Script.runInThisContext (vm.js:50:33)
at Object.runInThisContext (vm.js:139:38)
at Object.<anonymous> ([eval]-wrapper:6:22)
at Module._compile (module.js:653:30)
at evalScript (bootstrap_node.js:479:27)
at startup (bootstrap_node.js:180:9)
at bootstrap_node.js:625:3
Unfortunately, I cannot debug this by myself. What am I doing wrong? Can you help me?
Explanation
I have a docker puppeteer container with node myself and it works, I am just curious to test with your container as I stumbled upon a recommendation somewhere.
My container use has to be throttled somewhat as CPU tends to rise when too many parallel requests are running. I suppose this is perfectly normal, but maybe your solution works better.
The text was updated successfully, but these errors were encountered:
Hello, as far as I can see your example should work out of the box, but it doesn't.
What did I do?
I put
example.js
to the root directory, made a subdirectoryoutput
from there and started your instruction:Unfortunately, I cannot debug this by myself. What am I doing wrong? Can you help me?
Explanation
I have a docker puppeteer container with node myself and it works, I am just curious to test with your container as I stumbled upon a recommendation somewhere.
My container use has to be throttled somewhat as CPU tends to rise when too many parallel requests are running. I suppose this is perfectly normal, but maybe your solution works better.
The text was updated successfully, but these errors were encountered: