@testcontainers/localstack fails when localstack:latest resolves to v4.x — "Ready" log message not received

[tzafrirben]

Expected Behaviour
Start LocalstackContainer with localstack/localstack:latest image

Actual Behaviour
When using LocalstackContainer with localstack/localstack:latest image, the container startup fails with:
Error: Log stream ended and message "Ready" was not received

Testcontainer Logs
Error: Log stream ended and message "Ready" was not received at LineStream.<anonymous> (node_modules/testcontainers/build/wait-strategies/log-wait-strategy.js:56:24)

Steps to Reproduce

import { LocalstackContainer } from '@testcontainers/localstack';

const container = await new LocalstackContainer('localstack/localstack:latest')
  .withEnvironment({ SERVICES: 'sqs' })
  .start();

Environment Information
@testcontainers/localstack: 11.13.0
testcontainers: 11.13.0
LocalStack image: localstack/localstack:latest (resolves to v4.x)
Node.js: 24
OS: Ubuntu 22.04 (GitHub Actions runner)

Workaround: Pin to localstack/localstack:3 (LTS) which reliably prints "Ready."
on startup.

[cristianrgreco]

Localstack v4 introduces a breaking change, more info here: #1274

You'll need to provide a LOCALSTACK_AUTH_TOKEN going forwards:

const localstack = await new LocalstackContainer("localstack/localstack:latest")
  .withEnvironment({ LOCALSTACK_AUTH_TOKEN: process.env.LOCALSTACK_AUTH_TOKEN ?? "" })

Not much Testcontainers can do here other than logging a warning or raising a runtime error, and updating docs.

Will track that as part of #1274.