Skip to content

cap-media-server Docker image not publicly accessible for self-hosting #1507

@julianwitzel

Description

@julianwitzel

Hi there! 👋
I'm trying to self-host Cap using the official docker-compose.template.yml and ran into an issue.

Description

The template references ghcr.io/capsoftware/cap-media-server:latest, but this image is not publicly accessible:

$ docker pull ghcr.io/capsoftware/cap-media-server:latest
Error response from daemon: error from registry: denied

The cap-web image pulls fine, but cap-media-server returns "denied".

Environment

Questions

  1. Is the cap-media-server image intentionally private?
  2. If so, is there an alternative for self-hosters, or can we run Cap without the media server?
  3. Would it be possible to make this image public for self-hosting users?

The self-hosting documentation doesn't mention that the media server is unavailable, so this might be worth clarifying.
Thanks for the great project! 🎬

Additional Context

  • Cap version: latest (Docker image ghcr.io/capsoftware/cap-web:latest)
  • Operating system, version: Ubuntu 24.04 LTS (Hetzner VPS)
  • Device: Server (self-hosted)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions