Closed yidasanqian closed 4 months ago
Since it's working fine locally, this likely has something to do with network access from the container. Try recording traces and compare them with local behavior to see which requests don't go through and why.
If you think this is a playwright issue, please file a new issue and provide a self contained example that doesn't depend on external servers (which may well return different results depending on where a request comes from).
Since it's working fine locally, this likely has something to do with network access from the container. Try recording traces and compare them with local behavior to see which requests don't go through and why.
If you think this is a playwright issue, please file a new issue and provide a self contained example that doesn't depend on external servers (which may well return different results depending on where a request comes from).
I set the timeout to 20 seconds locally and still get this error, but the website actually loads very quickly.
I checked the contents of trace.zip, and in reality, the main content loaded in about 3 seconds, but the total duration was around 23 seconds. Why did it take so long? Is there any way to speed up the loading time?
Version
1.43.0
Steps to reproduce
Expected behavior
I hope to see the webpage content load normally.
Actual behavior
Additional context
On my local Windows 11, running the same code directly through an IDE can load web content normally. But when I package it into a docker image and run it in a container environment, timeouts occur. What's even weirder is that some links can load web content normally, while others trigger timeouts that I can't control.
Environment
dockerfile part: