Skip to content

docs: use --pull always in protected-api sample to avoid stale SpiceDB image#64

Merged
miparnisari merged 1 commit into
authzed:mainfrom
ivanauth:fix/issue-59-sample-broken
Jul 9, 2026
Merged

docs: use --pull always in protected-api sample to avoid stale SpiceDB image#64
miparnisari merged 1 commit into
authzed:mainfrom
ivanauth:fix/issue-59-sample-broken

Conversation

@ivanauth

@ivanauth ivanauth commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Fixes #59.

The protected-api sample's README docker run reuses a locally-cached authzed/spicedb image. An image predating the v1 PermissionsService makes the sample crash on the first CheckPermissionAsync with:

Status(StatusCode="Unimplemented", Detail="unknown service authzed.api.v1.PermissionsService")

Add --pull always to the documented command so it always runs a current
image, plus a note calling out this failure mode.

Verified: docker run --pull always authzed/spicedb serve ... pulls the current image; grpcurl then lists authzed.api.v1.PermissionsService.

…thzed#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.
@miparnisari miparnisari merged commit b1a87cb into authzed:main Jul 9, 2026
4 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 9, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

dotnet sample does not work

2 participants