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

[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

• Ubuntu 24.04 LTS
• Docker 27.x
• Following the self-hosting docs at https://cap.so/docs/self-hosting

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)

[linear]

CAP-595

[Daandeve]

I'm having the same issue when deploying a new instance usinge the docker-compose.template.yml

[arfath77]

I am too facing the same issue, I do not see cap-media-server in the available package. @Daandeve @julianwitzel Could you please let me know if you were able to solve this?
Thanks!

[oskar-koli]

I was able to get the self hosting to work by just removing the references to the media server from the docker compose config. Seems that it isn't a mandatory dependency.

[richiemcilroy]

We'd need to confirm current registry visibility to act on this, and it's gone stale in the meantime. Please re-file if the cap-media-server image is still not accessible, noting exactly which registry and tag you tried.