Playwright CI with jammy container

Build a new docker image with the microsoft image as a base.

Then install all necessary stuff for your azure pipeline And push that docker image to a registry.

Then use that "custom" image for runs

instead of always installing stuff in the container, just build a new image with all of the stuff pre-installed

that was also an option... wondering if this problem was already solved before I went down all the possible routes! cheers @haze.dev

No worries. there might be a simpler answer to your solution.

The one i offered is how i usually would do it 🙂

The recommendation is curl -sL https://aka.ms/InstallAzureCLIDeb | bash inside the container which should be quite fast.

I did what @mxschmitt suggested. Works fine. It's not "quite fast"... but this is a side project, doesn't hurt.

-  Install Az Client  3m 12s
-  Login to Azure     4s
-  Run Tests          1m 51s

[...]

jobs:
  build:
    name: 'Build'
    runs-on: ubuntu-latest
    container:
      image: mcr.microsoft.com/playwright/dotnet:v1.32.0-jammy
    steps:
      - uses: actions/checkout@v3
      - name: Setup dotnet
        uses: actions/setup-dotnet@v3
        with:
          dotnet-version: 7.0.x
      - run: dotnet build
      - name: Install Az Client
        run: curl -sL https://aka.ms/InstallAzureCLIDeb | bash
      - name: Login to Azure
        run: az login --service-principal --username ${{ secrets.servicePrincipalId }} --password ${{ secrets.servicePrincipalKey }} --tenant ${{ secrets.tenantId }}
      - name: Run Tests
        run: dotnet test

[...]

But works, if people are facing a similar issue and while they work on other solutions... at least, unblocks the pipeline.