Skip to content

Container image is private, so the README's docker run fails for everyone #30

Description

@adityak74

README.md offers the container as the try-it-without-installing path:

docker run --rm -v "$PWD":/work \
  -e ZORP_BASE_URL -e ZORP_MODEL -e ZORP_API_KEY \
  ghcr.io/aviskaar/zorp "<your task>"

Anonymously, that fails:

$ docker logout ghcr.io && docker pull ghcr.io/aviskaar/zorp:latest
Error response from daemon: error from registry: unauthorized

The manifest API agrees: HTTP 403 for an anonymous token.

The image builds and publishes fine (the Image workflow is green and
smoke-tests --version on both arches). It is only the package's
visibility, which defaults to private even when the repository is public.

Fix: set the package to public at
https://github.com/orgs/aviskaar/packages/container/zorp/settings

This needs admin:packages on a human account and cannot be done from
the REST API, which has no visibility endpoint for packages.

Until then the README carries a note pointing here. Closing this issue
means deleting that note.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions