Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Docker image fails to run when using the recommended Docker file from this repo #2668
I created a Nuxt.js application which uses Puppeteer in an express end point. The application only works on localhost Mac OS. When I run the application in Cloud Foundry Linux Debian that specific route times out as I have seen other people on the internet have the same problem when deploying to a Debian production environment.
Due to this, I decided to use the Docker example from this repo. I put my application in Docker and was able to replicate my initial issue. At this point I moved to update the Docker file with the recommended Docker file in this repo which has since then produced this error.
I have tried every thing that exists on the internet to overcome this. What steps must I take beyond the recommendation for the Docker file to run this image?
I would be happy to run it as root with --no-sandbox but I am not sure how that can be done from the Docker file.
Due to the trouble I have faced I am wondering if this is a bug?
What steps will reproduce the problem?
Create Docker file, paste the Docker file from this repo in and
Then run -
Please include code that reproduces the issue.
My Docker file -
My run command -
What steps further must be taken to run this image?
What is the expected result?
What happens instead?
have you tried not using the
The problem is that the env you run the container on matters. For example, if it doesn't support namespaces then adding a user and running chrome/puppeteer as that user won't work :(
Not sure what Cloud Foundry Linux Debian contains. I can test our Dockerfile again to make sure it's still working and up to date, but maybe we should be recommending
Here is what finally worked for me,
Then I ran Puppeteer like this,
After days of working on this, it finally works with this config. I am not sure what the major differences are between what I have and what was suggested. But I can say that this works perfectly.
I second this issue, I tried to run pptr with a similar Dockerfile (node8-slim, chrome-stable, add pptruser, dumb-init) and got the same error when launched without the
I think you're the best judges on this matter, in my situation the container will run in my company private network so I'm not that concerned by security but I can see usecases where this is important.