[Bug]: Docker Redis Insight does not detect Redis Search when opening a preconfigured database through a direct route
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.8k
- Forks
- 491
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Preconditions
Docker Redis Insight is started as a fresh instance.
The Redis database connection is preconfigured through Docker environment variables:
RI_REDIS_HOST=redis
RI_REDIS_PORT=6379
RI_REDIS_ALIAS=Workshop Redis
RI_ACCEPT_TERMS_AND_CONDITIONS=true
The target Redis database has Redis Search enabled.
Steps to reproduce
-
Start Docker Redis Insight with a preconfigured Redis database connection.
-
Open Redis Insight directly at:
http://localhost:5540/0/vector-search
-
Observe the Search page.
-
Go back to the database picker:
http://localhost:5540/
-
Click the same preconfigured database.
-
Open the Search tab again.
Actual behavior
When Docker Redis Insight is opened directly at /0/vector-search, the Search page says:
Redis Query Engine is not available for this database
After entering the same preconfigured database through the database picker, the Search page loads correctly.
Expected behavior
Docker Redis Insight should detect Redis Search for the preconfigured database when opening /0/vector-search or /0/browser directly.
Additional context
Host OS: macOS 15.7.4
Redis Insight distribution: Docker version
Redis Insight version: 3.6.0
Redis Insight build type: Docker on premise
Redis Insight image: redis/redisinsight:latest
Image SHA: sha256:aa21bbd198455b4ad964f76782db951155aa0d712321f599972d1525f031f0e6
Redis database version: 8.8.0
Database type: Standalone
Connection type: Standalone
Redis Search module version: 80800
Redis JSON module version: 80800
Redis TimeSeries module version: 80800
No browser console errors were observed during reproduction.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the direct /0/vector-search and /0/browser routes with the documented Docker environment variables, then compare their database initialization with entering through /. Verify that the preconfigured database detects Redis Search and that the Search page loads correctly on both direct routes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, redis, typescript
- Domain
- database, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100