[Bug]: Unable to pull ryuk image.
Testcontainers version
3.10.0
Using the latest Testcontainers version?
Yes
Host OS
Linux
Host arch
x64
.NET version
.NET 8.0.8
Docker version
27.3.1
Docker info
Client: Docker Engine - Community
Version: 27.3.1
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.17.1
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.29.7
Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 5
Running: 4
Paused: 0
Stopped: 1
Images: 25
Server Version: 27.3.1
Storage Driver: overlay2
Backing Filesystem: btrfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
runc version: v1.1.14-0-g2c9f560
init version: de40ad0
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.10.9-200.fc40.x86_64
Operating System: Fedora Linux 40 (Workstation Edition)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.38GiB
Name: fedora
ID: c6082888-9771-4e10-921d-30a3ef6f6cf6
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Live Restore Enabled: false
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
What happened?
Setup failed for test fixture Authentica.Service.Identity.Tests.IntegrationTests.AccountPurgeBackgroundServiceTests System.AggregateException : One or more errors occurred. (Docker API responded with status code=InternalServerError, response={"message":"Head "[https://registry-1.docker.io/v2/testcontainers/ryuk/manifests/0.6.0](https://registry-1.docker.io/v2/testcontainers/ryuk/manifests/0.6.0/)": unauthorized: incorrect username or password"}
Relevant log output
No response
Additional information
No response
unauthorized: incorrect username or password
Can you please make sure you are using the correct credentials (for Docker Hub) and try it again? I think Docker had an outage yesterday too.