Release 11.7.0: An error occurred getting a credentia

[Jank1310]

Expected Behaviour
Run tests / pull images successfully (works in 11.6.011.5.1)

Actual Behaviour
Setup of tests / containers fails
Running tests with DEBUG log enabled shows:

Testcontainer Logs

2025-10-01T07:03:36.216Z testcontainers [DEBUG] Pulling image "testcontainers/ryuk:0.14.0"...
2025-10-01T07:03:36.217Z testcontainers [DEBUG] Executing Docker credential provider "docker-credential-desktop"
2025-10-01T07:03:36.303Z testcontainers [ERROR] An error occurred getting a credential: 1

Steps to Reproduce

1. Install version 11.7.0
2. Run await new MongoDBContainer("mongo:8").start()
3. See error "An error occurred getting a credential"

Environment Information

• Operating System: OSX 15.7.1
• Docker Version:

Client: Docker Engine - Community
 Version:           28.4.0
 API version:       1.51
 Go version:        go1.25.0
 Git commit:        d8eb465f86
 Built:             Wed Sep  3 20:52:20 2025
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.47.0 (206054)
 Engine:
  Version:          28.4.0
  API version:      1.51 (minimum version 1.24)
  Go version:       go1.24.7
  Git commit:       249d679
  Built:            Wed Sep  3 20:58:53 2025
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.7.27
  GitCommit:        05044ec0a9a75232cad458027ca83437aae3f4da
 runc:
  Version:          1.2.5
  GitCommit:        v1.2.5-0-g59923ef
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

• Node version: 24.9.0
• Testcontainers version: 11.7.0

[AndreKlang]

I had the exact same issue just now, did a docker pull testcontainers/ryuk:0.14.0, and it worked.. Not sure what to make of that..

[digital88]

I too had this on fresh windows + docker desktop env, checkouted main branch somewhere between 11.6 and 11.7.

Pulled ryuk manually using docker pull, didn't have much time to investigate it.

Maybe this is caused by newer docker (desktop) ?

[cristianrgreco]

My guess would be it's related to #1121, which was released in 11.6.0, but you are only seeing the issue in 11.7.0 because the Ryuk image was bumped, resulting in a new pull. Could you please confirm by removing the ryuk image (both versions 0.13 and 0.14!), and trying again with testcontainers-node 11.6.0?

[Jank1310]

Sorrvey I should've mentioned that the error occurs for different containers/images not just for ryuk
Another example

2025-10-01T11:26:18.811Z testcontainers [DEBUG] Checked if image exists "mongo:8
2025-10-01T11:26:18.811Z testcontainers [DEBUG] Pulling image "mongo:8"...
2025-10-01T11:26:18.811Z testcontainers [DEBUG] Executing Docker credential provider "docker-credential-desktop"
2025-10-01T11:26:18.876Z testcontainers [ERROR] An error occurred getting a credential: 1
2025-10-01T11:26:18.876Z testcontainers [ERROR] Failed to pull image "mongo:8": Error: An error occurred getting a credential

[Jank1310]

@cristianrgreco It seems that your guess is correct:

• Image pull + version 0.16.0 or 0.17.0 => error.
• Image pull + version 0.15.1 => works

@AndreKlang Solution prevents pulling but you have to make sure that all other images are local available too

[cristianrgreco]

I'll likely rollback that change and release a patch. Before I do could you please help me debug just in case I can fix forward? Could you please run some of these commands, taking care to omit sensitive values, and let me know what you get?

cat ~/.docker/config.json

{
	"auths": {
		"https://index.docker.io/v1/": {},
	},
	"credsStore": "desktop"
}

Same with this command: docker-credential-desktop list. Mine is:

{
  "https://index.docker.io/v1/": "..."
}

And finally same with echo 'https://index.docker.io/v1/' | docker-credential-desktop get:

{
  "ServerURL": "https://index.docker.io/v1/",
  "Username": "...",
  "Secret": "..."
}

[digital88]

I can share mine:

.docker\config.json:

{
	"auths": {},
	"credsStore": "desktop",
	"currentContext": "desktop-linux"
}

docker-credential-desktop list:

{}

echo 'https://index.docker.io/v1/' | docker-credential-desktop get:

credentials not found in native keychain

[cristianrgreco]

Thanks @digital88.

That confirms it then, we try to look up credentials for the default index registry URL (https://index.docker.io/v1/), and in this case there are none. Previously we would return undefined, i.e. there are no credentials, but now we optimistically run the credential provider, which in your case (and many others I guess) throws.

@karol-bochenski I guess we forgot to catch the error and return empty credentials if getting the credential fails. My first thought is to do exactly this, do you have any thoughts?

[Jank1310]

I have the same output as @digital88

[cristianrgreco]

Preparing a fix #1153. If no issues will release a patch today.