
You should find Puppeteer executes successfully, provided proper Chrome flags are used. We need to import the following namespaces: using PuppeteerSharp using System. We can do this by using the below command: dotnet add package PuppeteerSharp Once the package is installed, we can start writing some code. Chrome will write into /tmp instead.Īdd your JavaScript to your container with a COPY instruction. First, we need to install the Puppeteer Sharp NuGet package in your dotnet core project.

disable-dev-shm-usage – This flag is necessary to avoid running into issues with Docker’s default low shared memory space of 64MB.If you’re uncomfortable with this, you’ll need to manually configure working Chrome sandboxing, which is a more involved process. It’s vital you ensure your Docker containers are strongly isolated from your host. Using these flags could allow malicious web content to escape the browser process and compromise the host. no-sandbox and disable-setuid-sandbox – These disable Chrome’s sandboxing, a step which is required when running as the root user (the default in a Docker container).Setting this flag explicitly instructs Chrome not to try and use GPU-based rendering. disable-gpu – The GPU isn’t usually available inside a Docker container, unless you’ve specially configured the host.
