search

alekzonder / docker-puppeteer

docker image with Google Puppeteer installed
https://hub.docker.com/r/alekzonder/puppeteer/
MIT License
485 stars 138 forks source link

Error: spawn EACCES #9

Open eskimoblood opened 6 years ago

eskimoblood commented 6 years ago

The version 1.1.0 throws an Error: spawn EACCES when I try to launch puppeteer. Not sure if this important but I have puppeteer installed locally in my project.

alekzonder commented 6 years ago

@eskimoblood need more info, what javascript script you run inside docker, how you mount it your project scripts into container

paste here your docker run ... with all arguments

Neoglyph commented 6 years ago

EDIT: Found a solution to my question below

Since mapping my custom folder to the root app folder had seemingly overriden the node_modules too, the puppeteer dependency did not exist.

the solution was to map one level lower: docker run --shm-size 1G --rm -v /home/test/code/test:/app/test alekzonder/puppeteer:latest node test/index.js

Same here. When trying to launch my script with the command: docker run --shm-size 1G --rm -v /home/test/code/test:/app alekzonder/puppeteer:latest node index.js

I get the following: 

{ Error: spawn EACCES
    at _errnoException (util.js:1022:11)
    at ChildProcess.spawn (internal/child_process.js:323:11)
    at Object.exports.spawn (child_process.js:502:9)
    at Function.launch (/app/node_modules/puppeteer/lib/Launcher.js:107:40)
    at <anonymous> code: 'EACCES', errno: 'EACCES', syscall: 'spawn' }

Additional info: The script seemingly runs fine (since I've managed to print out my arguments just fine until it reaches this part:

puppeteer.launch({
  args: [ '--no-sandbox', '--disable-setuid-sandbox' ]
})

This works just fine with: run --shm-size 1G --rm -v /home/test/code/test/index.js:/app/index.js alekzonder/puppeteer:latest

but that's not an option since I need to pass additional arguments to the script.

isakatirci commented 3 years ago

what is root password. help. sudo does not work!