Skip to content
This repository has been archived by the owner on Nov 20, 2023. It is now read-only.

Cannot run a dapr service that does not expose HTTP #1172

Closed
paulyuk opened this issue Sep 20, 2021 · 0 comments · Fixed by #1194
Closed

Cannot run a dapr service that does not expose HTTP #1172

paulyuk opened this issue Sep 20, 2021 · 0 comments · Fixed by #1194
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@paulyuk
Copy link

paulyuk commented Sep 20, 2021

Describe the bug

Today, it looks like the Dapr sidecar only loads if the binding is set to HTTP. That is a catch 22 for a non http service, like a headless client or server. If the service binding is set to HTTP then tye will wait to see that port get exposed before running. And if you turn off HTTP, then sidecar will not load.

To Reproduce

  1. Clone the Dapr Hello-world quickstart from this fork branch:
    https://github.com/paulyuk/quickstarts/tree/paulyuk/tye
    git clone -b paulyuk/tye https://github.com/paulyuk/quickstarts.git

  2. cd to /quickstarts/hello-world

  3. Per the readme, do the npm install, and pip3 commands to restore packages.

  4. tye run
    ** the pythonapp sidecar will not load, so this service cannot resolve the name and port of nodeapp

  5. uncomment the explicit 5000 port binding for pythonapp
    https://github.com/paulyuk/quickstarts/blob/paulyuk/tye/hello-world/tye.yaml#L30

sadly, the app still breaks because tye is waiting forever for this headless app to load on port 5000, which it isn't designed to do.

@paulyuk paulyuk added the bug Something isn't working label Sep 20, 2021
@philliphoff philliphoff self-assigned this Oct 5, 2021
@philliphoff philliphoff added enhancement New feature or request and removed bug Something isn't working labels Oct 5, 2021
@philliphoff philliphoff added this to the 0.11 milestone Oct 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants