-
Notifications
You must be signed in to change notification settings - Fork 202
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
Scheduler service is not started in self-hosted mode #1416
Comments
v1.14.0-rc.2 CLI fails to initialise the scheduler - everything else seems to have been initialised. |
I used
|
Just an observation, but I had several CI builds for the .NET SDK fail due to the Dapr installation step failing due to the |
I think my issue is now moving towards it being podman-specific now. Possibly an issue with the default mounts |
Seems to be a container mount permissions issue |
Expected Behavior
The scheduler should be started when using
dapr init
.Actual Behavior
Steps to Reproduce the Problem
Mac/Windows - Podman
Release Note
RELEASE NOTE:
The text was updated successfully, but these errors were encountered: