fix: test container setup with SigningKey

[bwaidelich]

Locally (MacBook M1) the EsdbClient testsuite currently fails for me with:

1. Thenativeweb\Eventsourcingdb\Tests\CloudEventSignatureTest::testVerifiesTheSignature
   RuntimeException: Failed to get mapped port ‘’ for container

2. Thenativeweb\Eventsourcingdb\Tests\CloudEventSignatureTest::testThrowsAnErrorIfTheSignatureVerificationFails
   RuntimeException: Failed to get mapped port ‘’ for container

3. Thenativeweb\Eventsourcingdb\Tests\CloudEventSignatureTest::testThrowsAnErrorIfTheHashVerificationFails
   RuntimeException: Failed to get mapped port ‘’ for container

With this change, tests are green again.

[bwaidelich]

Not sure why the CI fails, but apparently this needs some more work..

FYI: Without this change, the docker container logs

{"time":"2025-11-03T10:30:29.819048632Z","level":"ERROR","msg":"failed to execute command","error":"open /etc/esdb/signing-key.pem: no such file or directory"}

even though the following test script seems to yield valid results:

$signingKey = new SigningKey();
$container = (new GenericContainer('alpine'))
    ->withCommand(['tail', '-f', '/dev/null'])
    ->withCopyContentToContainer([[
        'content' => $signingKey->privateKeyPem,
        'target' => '/etc/esdb/signing-key.pem',
    ]])
    ->start();

$output = $container->exec(['cat', '/etc/esdb/signing-key.pem']);
$container->stop();

var_dump($signingKey->privateKeyPem);
var_dump($output);

=>

string(119) "-----BEGIN PRIVATE KEY-----
MC4CAQAwBQYDK2VwBCIEIHNdVTXkpg62smHk1gX4r2BQKHDsVVBj+31PSAvvy7Rp
-----END PRIVATE KEY-----
"
string(117) "w-----BEGIN PRIVATE KEY-----MC4CAQAwBQYDK2VwBCIEIHNdVTXkpg62smHk1gX4r2BQKHDsVVBj+31PSAvvy7Rp-----END PRIVATE KEY-----"

(not sure where the leading "w" comes from though)

[bwaidelich]

I could not let this go and jumped into the rabbit hole:

The leading "w" in the test above comes from a bug in the StartedGenericContainer::sanitizeOutput() implementation – but this only affects the debug script above and is unrelated.

The actual issue seems to be a "timing problem": at the time of running the command, the private key is not yet available on the container, i.e. it fails with open /etc/esdb/signing-key.pem: no such file or directory. Afterwards the file exists with -rwxrwxrwx permissions and running

eventsourcingdb run --api-token secret --data-directory-temporary --http-enabled --https-enabled=false --signing-key-file /etc/esdb/signing-ke
y.pem

manually works