wqy | wenquanyi open source Chinese font

You need to add the CMD and ENTRYPOINT to start your application in the Dockerfile. You missed it. So When you create the image from the Dockerfile and deploy it to the Web App, there is no application run as you expect.

So, I found the problem and document it here if it happens to someone else. It turned out to be how Visual Studio does the building now.

If I right-click and build the Dockerfile in Visual Studio the result will be correct just as my investigations above showed. The problem is that when I wanted to test the image, I run it by F5 (or Ctrl+F5) in VS and in that case Visual Studio does not build my Dockerfile by default. I thought that it used my recently build result (cached), but it actually uses another cached result. For performance reason it builds the project locally and take that result and adds it to the aspnet:3.1-buster-slim image, which means that my custom dependencies are not added.

This behaviour can be controlled by setting in the project file. The default value of if is Fast which does not use my Dockerfile, but setting it to Regular does, on the cost of slower start up. Documentation of this and other settings can be found here: https://docs.microsoft.com/en-us/visualstudio/containers/container-msbuild-properties?view=vs-2019

I am running chrome inside Cloud Run to transform webpages to PDF (and ten to SVG). Find my repo here

Here is my Dockerfile:

This is definitely matter of your proxy settings, not puppeteer nor docker. Unfortunately, I do not have access to your proxy, thus there's no way I could reproduce it. But first thing which comes to my mind - you usually have to authenticate when using https proxy. You can pass the username and password using page.authenticate before doing a navigation:

The solution comes from the original intent of the docker-compose.yml file which was converted into a kubernetes manifest via a tool called kompose. The original docker-compose file was intended for development and as such had overrides in place to push the local development environment into the running container.

This was because of this in the yml file:

You should pass --no-sandbox, --disable-setuid-sandbox args when launch browser. this is my docker file and small script. it's run successfully.

You can know more about puppeteer with docker by this references.

1. https://github.com/buildkite/docker-puppeteer
2. https://github.com/alekzonder/docker-puppeteer

Dockerfile

Posting my comment as an answer so this doesn't look like an unanswered question to people scrolling through:

Instead of open('/keep_2.pdf'), use open('/keep_2.pdf', 'rb') to open in binary mode.

Your build config is using node:latest as the base image. Apparently, that has been changed yesterday (see the README.md of node docker repository from version 13 to 14.

You could try downgrading the node image back to version 13:

I finally managed to get stencil working in a container suitable for Google Cloud Build. The main problem was that puppeteer, which is needed for e2e test, does not work as installed because it does not have a chrome install with all necessary dependencies.

To fix you have to do three things:

1. Install Chrome separately
2. Point puppeteer to the installed Chrome
3. Modify stencil config to invoke testing without a sandbox

1 & 2 are addressed with the following Dockerfile: