-
Notifications
You must be signed in to change notification settings - Fork 526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems Using Garnet Images in Aspire.Hosting.Redis #7024
Comments
@calmbino, Why do you use Garnet is not fully compatible with Redis. Garnet uses different approaches to persist data, Therefore you should use
I'm not sure See #4519 for |
@Alirexaa , First of all, thank you for your answer.
The answer to the above question is as follows.
I'm not exactly sure about this question. I haven't tested it outside of Aspire by connecting Garnet and RedisInsight. However, I applied the In conclusion, I'm not arguing that "Aspire.Hosting.Redis should support Garnet." I found a problem with a situation found during the testing process, and I wanted to communicate this situation. Now I know that if I have to use Garnet, I have to use Aspire.Hosting.Garnet. |
Closing as this question has been answered. |
I tried to use Garnet image on Aspire.Hosting.Redis as follows.
It runs normally and well. However, if you try to set the volume or mount for persistence, it will cause problems.
I refer to the execution log and the source code, I think the cause of the problem is that Garnet does not support the
-- save
optionsrc/Aspire.Hosting.Redis/RedisBuilderExtensions.cs
Of course, the above issue will be easily resolved by
not using Garnet images
or byusing Aspire.Hosting.Garnet
instead of Aspire.Hosting.Redis.But I think I can face the above problem situation because I know garnet is compatible with redis.
Anyway, if I want to use Garnet for now, would it be best to use Aspire.Hosting.Garnet?
And I was wondering if Aspire.Hosting.Garnet has any plans to add dashboard options like
RedisInsight
orRedisCommander
The text was updated successfully, but these errors were encountered: