[BUG] Playwright in docker stops working after release of the new version

[CyborTronik]

System info

• Playwright Version: [v1.39.0]
• Operating System: [All, Windows 11, Ubuntu 20, macOS 13.2, etc.]
• Browser: [ Chromium]
• Other info:

When the release of v1.40.0 happened the docker version of the v1.39 stopped working.
For some reason, it detects in real time that a new release happened and it tries to search the chromium binaries for v1.40 while being in a docker version of v1.39.

the version of v1.40 cannot be used in my project due to SDK 8 *while prev one is on .NET 6.

A workaround that can be used is to run playwright install again inside the container, which makes the whole idea of having an official container less favorable (and it is not a true immutable environment, which is sad).
This means legacy projects in a few years cannot be tested with a specific version of the docker container, and become unmaintainable.

[MindaugasMateika]

You need playwright and docker image version to be the same. It sounds like you don't lock your playwright dependency and it's upgraded automatically and thus you get the error you mentioned.

[mxschmitt]

Make sure as per above to use a pinned Docker image, e.g.:

  docker pull mcr.microsoft.com/playwright/dotnet:v1.40.0-jammy

and the same in your .NET package manager.

[CyborTronik]

Many thanks, for quick reaction, I mentioned specific version, which means to be tagged image.

…

On Tue, Jan 9, 2024, 10:06 AM Max Schmitt ***@***.***> wrote: Make sure as per above to use a pinned Docker image, e.g.: docker pull mcr.microsoft.com/playwright/dotnet:v1.40.0-jammy and the same in your .NET package manager. — Reply to this email directly, view it on GitHub <#28902 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAY7XMK3D5K6UGNWIUZHNUTYNUJBDAVCNFSM6AAAAABBSEHA22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBSG43DQNRRHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mxschmitt]

Can you give us the exact Docker image version and csproj file you are using? Maybe even a small repro repository which you can share with us so we can reproduce the error locally? This would help a ton in order to triage this issue more efficiently, thanks!

[dgozman]

Closing because we lack the information to act on this issue. If you can provide a full repro, please file a new issue by filling the "Bug Report" template, and link to this one.