We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mcr.microsoft.com/playwright:v1.40.0@sha256:9dcc823ba14151eecb81eedb3a0abcb4fac942ae7fa9c9f96fdfcc7f5db9d239
The docker images create the following errors. when you run npm behind a corporate proxy:
npm
This issue is known and fixed in node 20:
Please update to the newest node 20 version in the docker image, were this issue is fixed.
[EDIT] Seems to work with the current image mcr.microsoft.com/playwright:v1.40.1
mcr.microsoft.com/playwright:v1.40.1
The text was updated successfully, but these errors were encountered:
This should already be fixed in the future releases as we pull latest Node.js 20.x version when building the images.
Sorry, something went wrong.
I tried doing a workaround for this,
npm config set proxy $HTTP_PROXY npm config set https-proxy $HTTP_PROXY
I found that NO_PROXY still works as usual.
I wanted to use 1.40.1, but seems it is only partially released, npm and docker is available, but not java / maven?
mxschmitt
No branches or pull requests
System info
mcr.microsoft.com/playwright:v1.40.0@sha256:9dcc823ba14151eecb81eedb3a0abcb4fac942ae7fa9c9f96fdfcc7f5db9d239
Issue
The docker images create the following errors. when you run
npm
behind a corporate proxy:This issue is known and fixed in node 20:
Solution
Please update to the newest node 20 version in the docker image, were this issue is fixed.
[EDIT] Seems to work with the current image
mcr.microsoft.com/playwright:v1.40.1
The text was updated successfully, but these errors were encountered: