From ab202286b19d5dc6256f3f940644502a94c15d9d Mon Sep 17 00:00:00 2001 From: ivanauth Date: Tue, 16 Jun 2026 15:06:11 -0400 Subject: [PATCH] fix: use --pull always so the sample gets a current SpiceDB image (#59) The reported 'unknown service authzed.api.v1.PermissionsService' error is caused by a stale locally-cached authzed/spicedb image predating the v1 API, not by the released image being broken. Use --pull always to force a fresh pull rather than pinning to an aging version. --- examples/protected-api/README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/examples/protected-api/README.md b/examples/protected-api/README.md index 40a767c..d45730f 100644 --- a/examples/protected-api/README.md +++ b/examples/protected-api/README.md @@ -4,9 +4,12 @@ It uses the service dependency injection mechanism to stand up the gRPC services and provide them to the endpoint. ## Running the project -In a separate terminal, set up a running spicedb instance: +In a separate terminal, set up a running spicedb instance. `--pull always` +ensures you get a current image; a stale locally-cached `authzed/spicedb` +predating the v1 PermissionsService is the usual cause of +`unknown service authzed.api.v1.PermissionsService` errors. ```bash -docker run --rm -p 50051:50051 authzed/spicedb serve --grpc-preshared-key lovelycoconuts +docker run --pull always --rm -p 50051:50051 authzed/spicedb serve --grpc-preshared-key lovelycoconuts ``` Write the schema from the resources folder to the SpiceDB server: