Azure Devops, DynamoDB and TestContainers

[dsshep]

Hi,

I have a test containers test, using the amazon/dynamodb-local official AWS DynamoDB image.

I'm trying to run the test in Azure Devops pipelines, but the container never seems to go healthy and times out after ~4 minutes after the call to StartAsync. Subsequently trying to create tables against the container fail.

The container configuration looks something like:

var builder = new TestcontainersBuilder<TestcontainersContainer>()
       .WithImage("amazon/dynamodb-local:latest")
       .WithCleanUp(true)
       .WithPortBinding(10001, 8000);

dynamoDbContainer = builder.Build();

await dynamoDbContainer.StartAsync();

Is there anything I am missing here? Is there an easy way to attach some logging mechanism to get some insight as to what may be going wrong?

[HofmeisterAn]

Does your configuration run on your local machine? You can configure logging and forward stdout and stderr with an output consumer, but somehow DynamoDBLocal.jar does not write to stdout (at least that is what I noticed in a quick test). Getting the logs otherwise is not yet supported (but I can add it, it is not much to do).

You can disable the resource reaper (TestcontainersSettings.ResourceReaperEnabled = false), run your configuration and get the logs with the CLI docker logs CONTAINER (set the container name with WithName())?

[HofmeisterAn]

Maybe a repo example in devops may be needed

Yep, that would be nice. The configuration looks good so far. If you have something I can play around with, I can take a look at it.

[dsshep]

I've created a repo here. Let me know if you have trouble viewing it.

In the process of putting this together, I noticed that the tests run fine through Visual Studio, but don't seem to be happy in dotnet test or dotnet vstest... So perhaps not related to the pipeline after all?

[HofmeisterAn]

In the process of putting this together, I noticed that the tests run fine through Visual Studio, but don't seem to be happy in dotnet test or dotnet vstest... So perhaps not related to the pipeline after all?

Ok, I will take a look at it.

[HofmeisterAn]

I am not an AWS (DynamoDB) expert, but I assume your issue relates too: https://stackoverflow.com/a/62061272. I guess you are using an AWS profile in Visual Studio. The pipeline runs fine when I provide the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables: 150fa7c3. Dunno if that is the right fix.

[dsshep]

That was the problem. Thank you so much, you're a hero!