Not able to run redis from Docker Desktop for an Aspire application

[dipudivakaran79]

I was trying to run redis from the docker desktop using an Azure Aspire application. Here is what I see from the docker desktop logs.

7:C 21 Dec 2025 18:22:25.950 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

7:C 21 Dec 2025 18:22:25.950 * Redis version=7.4.7, bits=64, commit=00000000, modified=0, pid=7, just started

7:C 21 Dec 2025 18:22:25.950 * Configuration loaded

7:M 21 Dec 2025 18:22:25.950 * monotonic clock: POSIX clock_gettime

7:M 21 Dec 2025 18:22:25.952 * Running mode=standalone, port=6380.

7:M 21 Dec 2025 18:22:25.956 # Failed to configure CA certificate(s) file/directory: error:80000002:system library::No such file or directory

7:M 21 Dec 2025 18:22:25.956 # Failed to configure TLS. Check logs for more info.

Initial Code was to run the latest version of the redis continer. Since it is the latest version and having more difficulty in running in windos machine, I have tried to run more specific verion . However, both cases, I am getting the same result. Do we have any experts who can help on it?

var cache = builder
.AddRedis("cache")
.WithRedisInsight()
.WithImage("redis")
.WithImageTag("7.4")
.WithDataVolume()
.WithLifetime(ContainerLifetime.Persistent);

Original code used was below.

var cache = builder
.AddRedis("cache")
.WithRedisInsight()
.WithDataVolume()
.WithLifetime(ContainerLifetime.Persistent);

Thanks
Dipu

[davidfowl]

cc @danegsta

[danegsta]

@dipudivakaran79 while your host OS may be Windows, your containers are running in a Linux VM (either a WSL2 distro or a full Hyper-V VM depending on how you have things configured), so there shouldn’t be any reason to need to downgrade your Redis version from the latest.

As for the error, it seems the HTTPS certificate we configure isn’t being added to your container correctly. Can you double check in your Docker Desktop settings if you’re configured to use WSL2 or Hyper-V to run your containers?

You can see if there’s an issue with the ASP.NET developer certificate that’s causing an issue by running dotnet dev-certs https —clean followed by dotnet dev-certs https —trust to refresh the certificate. Finally, you can disable the HTTPS feature for your Redis container if none of the troubleshooting works: https://aspire.dev/app-host/certificate-configuration/#disable-https-certificate-configuration