CI/CD pipelines

[milkshakeuk]

How does this work with Azure DevOps pipelines or GitHub actions? Does it "just work" or is this library only useful in a local developer environment?

Any Azure DevOps and GitHub Actions yml examples would be awesome.

[HofmeisterAn]

Testcontainers runs on CI / CD too. All tests in this library run on GitHub Actions and previous on Azure DevOps Pipelines. I've used it on Jenkins, GitLab and Bitbucket Pipelines too.

[Marsellus47]

How can I use a private Azure container registry in Azure DevOps pipeline? I'm getting the following error:

Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"Head \"https://<my registry>.azurecr.io/v2/<my image>/manifests/latest\": unauthorized: authentication required, visit https://aka.ms/acr/authorization for more information."}

I have the following task in Azure DevOps pipeline:

- task: AzureCLI@2
  displayName: Test
  inputs:
    azureSubscription: <my service connection with AcrPull role>
    scriptType: pscore
    scriptLocation: inlineScript
    inlineScript: |
      az acr login --name <my registry>
      dotnet test <my solution>.sln --no-build --configuration Release

The tests work locally as my user has access to the Azure container registry

[Marsellus47]

Nevermind, I made it work using the following tasks:

- task: Docker@2
  displayName: Docker login
  inputs:
    containerRegistry: <service connection of type Docker Registry>
    command: login

- task: DotNetCoreCLI@2
  displayName: Test
  inputs:
    command: test
    projects: '**/*Tests/*.csproj'
    arguments: '--no-build --configuration Release'

[HofmeisterAn]

That's the right approach.

[intrepid-developer]

I'm have a similar issue in GitHub Actions when trying to access the GitHub Container Repo.

name: 'Run Tests'

on:
  workflow_call:
    inputs:
      CSPROJ_PATH:
        required: true
        type: string

permissions:
  packages: read
  contents: read

jobs:
  tests:
    runs-on: ubuntu-latest
    timeout-minutes: 45
    env:
      DOTNET_CLI_TELEMETRY_OPTOUT: true
    steps:
      - name: 'Checkout code'
        uses: actions/checkout@v4

      - name: 'Use .NET'
        uses: actions/setup-dotnet@v4
        with:
          dotnet-version: '8.0.x'
     
      - name: Log in to GitHub Container Registry
        uses: docker/login-action@v3
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ github.token }}     

      - name: 'Run Tests'
        uses: nick-fields/retry@v3
        with:
          timeout_minutes: 30
          max_attempts: 2
          retry_wait_seconds: 30
          command: dotnet test ${{ inputs.CSPROJ_PATH }}

However when our tests run we still get these errors:

Failed to start container
---- Docker.DotNet.DockerApiException : Docker API responded with status code=InternalServerError, response={"message":"denied"}

[HofmeisterAn]

response={"message":"denied"}

Does the token have the necessary permissions? It looks like Testcontainers is finding the credentials, but they don’t have the required permissions. Could you also share the Testcontainers log messages?

[intrepid-developer]

@HofmeisterAn thank you for the quick response. For now we've switched to using a PAT (classic) instead which seems to have solved the issue. It is definitely a problem with the permissions for the token that the GH Action gets. We added a testing step to try and pull the image and that showed us the token it was getting wasn't working, even though the docker/login-action step was saying login: successful

I'm not sure why this isn't giving the action the correct permissions:

permissions:
  packages: read
  contents: read

Especially given the PAT we've created only has this permission: read:packages

So might be something with how GitHub actually handles action permissions. We've got a workaround for now though 😄