Skip to content
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

Unable to run examples #20

Open
gmtek opened this issue Sep 4, 2024 · 3 comments
Open

Unable to run examples #20

gmtek opened this issue Sep 4, 2024 · 3 comments

Comments

@gmtek
Copy link

gmtek commented Sep 4, 2024

I am trying to run SpiceDB in my local. After docker compose -f datastor/postgres.yml up when I am trying to connect using zed, getting error. It seems like zed is forcing TLS. Also there is nothing in http://localhost:8080. Is there any other configuration that SpiceDB container is expecting?

docker compose -f datastor/postgres.yml
zed --insecure context set dev 'http://127.0.0.1:50051' 'foobar'
zed --insecure schema write schema.md

12:40PM FTL failed to write schema error="failed to exit idle mode: invalid target address http://127.0.0.1:50051, error info: address http://127.0.0.1:50051:443: too many colons in address"

The containers are running. Below is output from docker ps

CONTAINER ID   IMAGE                          COMMAND                  PORTS  
a9a64714787d   authzed/spicedb:latest-debug   "spicedb serve"          0.0.0.0:8080->8080/tcp, 0.0.0.0:9090->9090/tcp, 0.0.0.0:50051->50051/tcp   
c073611766b0   postgres                       "docker-entrypoint.s…"   0.0.0.0:5432->5432/tcp   
@TWinsnes
Copy link

TWinsnes commented Sep 4, 2024

If you remove the http:// from the host it should work

And you can add --insecure to the context set command and you don't have to use the --insecure flag anymore after that when using zed

My set context command:
zed ctx set dev localhost:50051 TestKey --insecure

@gmtek
Copy link
Author

gmtek commented Sep 4, 2024

Wow, that works.

Can't access Dashboard at localhost. Is there any specific config needs to be done for the dashboard?

curl -k 'http://localhost:8080/'

curl: (52) Empty reply from server

@tstirrat15
Copy link

@gmtek the dashboard was removed from SpiceDB a while ago - it served a text version of the schema and didn't provide a whole lot of other value.

Where did you see reference to the dashboard? I wanna make sure we're not directing users to access it in our materials.

What's the use case? Is it mostly seeing whether SpiceDB is up? You can turn on the HTTP server if that'd help - you'd be able to hit /healthz with curl and get a 200.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants