You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dapr init skips checking redis container and not error is printed.
$ dapr init --redis-host testhost
⌛ Making the jump to hyperspace...
← Downloading binaries and setting up components... You have specified redis-host: testhost. Make sure you have a redis server running there.
→ Downloading binaries and setting up components...
Dapr runtime installed to $HOME/.dapr/bin, you may run the following to add it to your path if you want to run daprd directly:
export PATH=$PATH:$HOME/.dapr/bin
✅ Downloaded binaries and completed components set up.
ℹ️ daprd binary has been installed to $HOME/.dapr/bin.
ℹ️ dapr_placement container is running.
ℹ️ dapr_zipkin container is running.
ℹ️ Use `docker ps` to check running containers.
✅ Success! Dapr is up and running. To get started, go here: https://aka.ms/dapr-getting-started
Actual Behavior
$ dapr init --redis-host testhost
⌛ Making the jump to hyperspace...
← Downloading binaries and setting up components... You have specified redis-host: testhost. Make sure you have a redis server running there.
← Downloading binaries and setting up components...
Dapr runtime installed to $HOME/.dapr/bin, you may run the following to add it to your path if you want to run daprd directly:
export PATH=$PATH:$HOME/.dapr/bin
✅ Downloaded binaries and completed components set up.
ℹ️ daprd binary has been installed to $HOME/.dapr/bin.
ℹ️ dapr_placement container is running.
❌ container dapr_redis is not running
Steps to Reproduce the Problem
Run dapr init --redis-host testhost
Release Note
RELEASE NOTE: SKIP container check for Redis when --redis-host is specified.
The text was updated successfully, but these errors were encountered:
When a non-default redis host is specified during init, we do not
try and start the container and assume the user has set it up
correctly. This commit stops an errant error message from dapr
checking if the container is present/running.
dapr#479
When a non-default redis host is specified during init, we do not
try and start the container and assume the user has set it up
correctly. This commit stops an errant error message from dapr
checking if the container is present/running.
#479
Co-authored-by: Mukundan Sundararajan <musundar@microsoft.com>
Dapr is still installed in self-hosted mode.
But there is an error printed at the end of init.
Expected Behavior
Dapr init skips checking redis container and not error is printed.
Actual Behavior
Steps to Reproduce the Problem
Run
dapr init --redis-host testhost
Release Note
RELEASE NOTE: SKIP container check for Redis when --redis-host is specified.
The text was updated successfully, but these errors were encountered: