Update Redis Commander container image to ghcr.io/joeferner/redis-commander

[Copilot]

Description

The Redis Commander container image has moved registries. The old docker.io/rediscommander/redis-commander image is no longer maintained and causes the UI to fail loading with endpoint resolution errors.

Changes:

• Updated RedisCommanderRegistry from docker.io to ghcr.io
• Updated RedisCommanderImage from rediscommander/redis-commander to joeferner/redis-commander

Container will now pull: ghcr.io/joeferner/redis-commander:latest

Fixes #(issue)

Checklist

• Is this feature complete?
  • [x] Yes. Ready to ship.
  • [ ] No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • [x] Yes
  • [ ] No
• Did you add public API?
  • [ ] Yes
    • If yes, did you have an API Review for it?
      • [ ] Yes
      • [ ] No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • [ ] Yes
      • [ ] No
  • [x] No
• Does the change make any security assumptions or guarantees?
  • [ ] Yes
    • If yes, have you done a threat model and had a security review?
      • [ ] Yes
      • [ ] No
  • [x] No
• Does the change require an update in our Aspire docs?
  • [ ] Yes
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • [x] No

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Redis Commander image no longer works</issue_title> <issue_description>The Redis Commander image no longer works (UI never loads and the container logs are full of errors resolving the Redis container endpoint). The image registry is now ghcr.io/joeferner/redis-commander instead of docker.io/rediscommander/redis-commander. We need to update the corresponding entries in RedisContainerImageTags.cs.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes dotnet/aspire#12935

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions[bot]]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 12945

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 12945"

[github-actions[bot]]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 12945

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 12945"

[danegsta]

@radical I'm trying to update the image registry for Redis Commander (the official image is on ghcr.io now instead of docker.io), but it seems the test is timing out. I'm assuming it's a slow image pull causing issues. Have we considered updating our test image mirror to cover ghcr.io images as well as those on docker.io?

[radical]

@radical I'm trying to update the image registry for Redis Commander (the official image is on ghcr.io now instead of docker.io), but it seems the test is timing out. I'm assuming it's a slow image pull causing issues. Have we considered updating our test image mirror to cover ghcr.io images as well as those on docker.io?

@eerhardt ^