running sample - fail on redis

[codeputer]

Expected Behavior

After reading the ReadMe in ControllerSample, I would hope I could follow the example and have DAPR work as per the instructions. I'm new to all of this, so I'm hoping I'm missing something that I should have taken into account. I'm a C# microsoft stack developer no experience (or want) to play with other os, or languages at this poitn.

Actual Behavior

Dapr SampleController failes on "redispipe.connection". There is nothing that I can find regarding on redis in this regard - other than I know its storage for state? Redis? I thought DAPR could use Azure resources like CosmosDB, or perhaps Azure Table storage, which can be used locally as well.

Steps to Reproduce the Problem

dapr environment is setup and running, curl is installed. pasted in the commands, and it fails.

[jocko-wowza]

Based on the error, your DAPR application is trying to connect to a Redis server on Localhost. Are you currently running Redis locally?

If you don't it's possible that the CLI is injecting some default configurations into your components/ folder.

This bug talks about that concern #254

If you aren't running Redis locally, you should either delete any default files, or update them to include the connection information for your actual Redis server.

[codeputer]

The prerequisites of this example does not specify that redis is required. And or how to install before use. Can we specify local azure storage? As this was announced at an MS event, it would make sense that we would have samples from that tech stack. R Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: Jocko <notifications@github.com> Sent: Saturday, November 16, 2019 7:55:48 PM To: dapr/docs <docs@noreply.github.com> Cc: Richard Reukema <rreukema@hotmail.com>; Author <author@noreply.github.com> Subject: Re: [dapr/docs] running sample - fail on redis (#253) Based on the error, your DAPR application is trying to connect to a Redis server on Localhost. Are you currently running Redis locally? If you don't it's possible that the CLI is injecting some default configurations into your components/ folder. This bug talks about that concern #254 If you aren't running Redis locally, you should either delete any default files, or update them to include the connection information for your actual Redis server. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#253?email_source=notifications&email_token=AAEVJVNSRRYWPF7VJECPIO3QUCXDJA5CNFSM4JODLV5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIAHOI#issuecomment-554697657>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEVJVKI753QPTPR63YV4K3QUCXDJANCNFSM4JODLV5A>.

[jocko-wowza]

Your logs indicate that you're using Redis for PubSub and Statestore.

If you're not using these features, you can remove the component declarations from the components/ folder.

If you do want to setup Redis, this article exists and discusses how to setup a container, or an Azure cache:
https://github.com/dapr/docs/blob/master/concepts/components/redis.md#configuration

There are also sections for how to configure the Statestore and PubSub.

[codeputer]

Thanks very much for being patient with me in regard to these questions, it starting to make sense a bit! I attempted an Uninstall, and Init of Dapr [cid:image002.png@01D59D33.F0157A50] I must be working on the default configuration, as I don't have a component folder. 1. Is there a way to view the default configuration, or obtain a copy of the default configuration file for PubSub and Statestore? 2. How can I determine if redis is running locally within my configuration? 3. Is there an Azure Storage a component configuration for local state store using the local storage service from Azure? The last line in the documentation you referenced was: Standalone By default the Dapr CLI creates a local Redis instance when you run dapr init. However, if you want to configure a different Redis instance, create a directory named components in the root path of your Dapr binary and then copy your redis.yaml into that directory. Is there a default redis.yaml file, and can it be added as a component directory as opposed to a magic default configuration? Thanks very much for your time. Richard From: Jocko <notifications@github.com> Sent: November 17, 2019 10:33 AM To: dapr/docs <docs@noreply.github.com> Cc: Richard Reukema <rreukema@hotmail.com>; Author <author@noreply.github.com> Subject: Re: [dapr/docs] running sample - fail on redis (#253) Your logs indicate that you're using Redis for PubSub and Statestore. If you're not using these features, you can remove the component declarations from the components/ folder. If you do want to setup Redis, this article exists and discusses how to setup a container, or an Azure cache: https://github.com/dapr/docs/blob/master/concepts/components/redis.md#configuration There are also sections for how to configure the Statestore and PubSub. - You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://t.sidekickopen09.com/s1t/c/5/f18dQhb0S7lM8dDMPbW2n0x6l2B9nMJN7t5XWPfhMynW2B86_W5vMG5HW56dBWl7BRWd8102?te=W3R5hFj4cm2zwW3P28X24hCPvhW43T4NT3zfQ0QW3H8_MV1LyzF7W4hF7Zk1S3sRBW3K6K773ZRLC3W4hLxLG2fchJYW3SZ_xh3zhs7SW41Y1kQ3_R592W3vlmGS3K73rmW2nPn2z38jrbFW38mkbT2Rk0F9W1VdVcY2zNlfrW2zxp4b2nGHPvW2zMXqd2KDqMdW38593w3f__3jW38mlfy1Vg-1KW1YZVN91X6RDWW30kGP71W_NZVW38bCgY1VcDDwW38mLq22MF2DCW1ZfjD-3j8YlwW30qdXy3j6S-9W2xKcCY2CKzj1W4cPVPf3Fbt6_W3K78fL1Y_5qLn1--V_M103&si=8000000002124969&pi=d167a397-611f-4239-bfa7-73b2a409a4a0>, or unsubscribe<https://t.sidekickopen09.com/s1t/c/5/f18dQhb0S7lM8dDMPbW2n0x6l2B9nMJN7t5XWPfhMynW2B86_W5vMG5HW56dBWl7BRWd8102?te=W3R5hFj4cm2zwW3P28X24hCPvhW43T4P243X5bgW3SYLpP3T1MdZW1LFyV_4hCWypW49M7TJ1Gy80dW3Qzvpc2xQD4lW2Pw9HZ2KDrVPW30bz2y2zNkK_W2vQ08T1Y_8q5W2TqDYK32mtXMw2WpBMl5L72&si=8000000002124969&pi=d167a397-611f-4239-bfa7-73b2a409a4a0>.

[jocko-wowza]

Full disclosure @codeputer -- I'm not a direct contributor to the project, I'm another developer in your position, trying to get it functioning.

To answer your questions as best I can:

1. As I understand it, the components folder determines the configurations for the CLI. It's possible, that when the CLI doesn't have a components folder, it uses the default configuration. That's strictly a guess tho. In my experiences so far, adding the components directory and setting up components configurations for Statestore and PubSub has directed the CLI to use my configurations over any defaults.

2. I have discovered that the CLI/DAPR environment require Redis 5.x or higher because of streaming connection requirements. Making sure you have the correct version is important. The Redis quickstart has mechanisms to test a local installation of Redis (NOTE: You likely will have to have the DAPR CLI running to test):
   https://redis.io/topics/quickstart

3. I don't know specifically how to connect to Azure because I'm not directly implementing Azure resources. The component-contrib repo had descriptions of the various DAPR component implementations. I have found that these docs are still young, and could use some more details, but it should give you a rough idea of what resources can be used to back which DAPR functionalities: https://github.com/dapr/components-contrib

[codeputer]

Argh!! Found out after hours and hours that the "dapr init" was failing because, Docker was using WINDOW CONTAINERS! Why, why, why cant the init check to see if Docker is in this mode and give an intelligent error message. I then forked the documentation, and yup, its there - must use Linux containers... but in small print, and after it stays "Install Docker". As I had Docker installed, I missed that step in the deployment, and hence then also missed the Docker PS command to validate if it's all running or not.

[yaron2]

Hey @codeputer, Unfortunately the Docker API or CLI do not have a very good way of telling the daemon mode when running on Windows..

I've opened this PR in the CLI docs to make sure it is explicitly stated in the docs.

Thanks for reporting this.