[BUG] Screenshot of CJK languages from a Docker container is not working correctly
See original GitHub issueContext:
Full page screenshots of CJK (Chinese, Japanese, Korean) languages are not working when the Playwright script is running in a Docker container.
I’m testing with taking a screenshot of WordPress.com’s Japanese language signup page at the location https://wordpress.com/start/ja
with the following command:
await page.screenshot( {
path: `start_ja.png`,
fullPage: true,
type: 'jpeg',
quality: 20,
} );
This works well when I run the script on my local MacOS:
However, when the script runs from a Docker container, the screenshot looks like this:
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to Fix and Debug Docker Containers Like a Superhero
Container errors are tricky to diagnose, but some investigative magic works wonders. Read along to learn how to debug Docker containers.
Read more >Troubleshooting Docker client errors on Windows - Visual ...
Troubleshoot problems you encounter when using Visual Studio to create and deploy web apps to Docker on Windows by using Visual Studio.
Read more >How to Write Cleaner, Safer Code with SonarQube, Docker ...
In this post, I'll show you how to run a Docker container with SonarQube to analyze ... SonarQube can highlight issues and bugs...
Read more >Docker for Development: Common Problems and Solutions
That's because signals from the shell are not properly sent to your docker container. Just use dumb-init. It is a great, small wrapper...
Read more >Use Docker Compose to work with multiple containers
This file provides a simplified mode for starting that enables the debugger. Screenshot of project with docker-compose files. The VS Code Docker extension ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Our custom Docker image used
node:16.13.2-buster
as the base, which is in turn based on Debian. From my experiments so far, it appears that installingfonts-noto
resolves the problem.Closing as part of triage, but if you sort out which to use in your unofficial image, please comment here as it might be helpful for others in the community!