lkaklover.blogg.se

cache folder at the root of your node app would help but I doubt) and npm install.

Or please try again, remove puppeteerrc.cjs, set the env var in Render (maybe creating a. Then runtime would find try to change puppeteerrc.cjs to join(_dirname, 'project/src/' ,'.cache', 'puppeteer') I can not answer that didn't work for my case, imho there is a bug somewhere, when I tried a simple docker file to see the diffs with a Render install, something I noticed is that it was better to have Chrome being installed in /home/user/.cache/puppeteer and run the app with this user (moreover I don't want to fetch untrusted sites as root). cache but it still ended up in /root/.cache The directory I was configuring it wasn't even named. In other words, I added this last step to my why is it installing it there if I'm specifying a different directory to install in with. puppeteerrc.cjs and always used the default of /.cache/puppeteer.Īt this point I had already wasted too much time trying to figure it out so I gave up and just copied the default cache directory from the base stage of the Docker container to the release stage. The resulting container did not have the cache directory I added in the. I made sure to docker-compose build a fresh empty image with no cache to guarantee that puppeteer was seeing the configuration file and using it to change its cache directory but it wasn't being picked up. Specifying a local cache directory through configuration as described in the documentation here worked locally after rm -rf node_modules and running npm i again, but for some reason it did NOT work in my Docker container 🤷‍♂️. I was not getting the error when running the app locally outside of Docker.

I was getting the error above when trying to use a Puppeteer based feature in a deployed environment which runs on a Docker container. I had the same issue and wanted to stop by and describe the solution I ended up going with in case it can help someone else.