Files
vectorize-io__hindsight/docker/docker-compose/pgroonga/Dockerfile
JiehoonKwak 5f1237279b fix(docker): repair PGroonga Compose image (#3316)
The PGroonga example referenced groonga/pgroonga:latest-debian-pg17, which has no registry manifest, so the documented Compose stack could not build.\n\nPin the current PGroonga 4.0.8 PostgreSQL 17 image and install pgvector 0.8.6 from the PGDG repository already configured by that base image. This removes the source clone and build toolchain while keeping the example on PostgreSQL 17 for parity with neighboring recipes.\n\nContext:\n- Fixes #3311.\n- Verified on arm64 with a disposable PostgreSQL instance.\n- CREATE EXTENSION vector and pgroonga both succeed.\n- Mixed Korean/English PGroonga search and pgvector distance queries pass.\n- PostgreSQL 18 deployment work remains a separate operational concern.
2026-08-10 12:05:51 +02:00

14 lines
633 B
Docker

# PostgreSQL with pgvector and pgroonga extensions.
#
# pgroonga is a multilingual full-text search extension built on Groonga.
# It works out of the box for CJK (Chinese, Japanese, Korean) and other
# non-whitespace-segmented languages via the TokenBigram tokenizer.
FROM groonga/pgroonga:4.0.8-debian-17
# Install pgvector on top of the pgroonga base image (which already provides
# pgroonga, the Groonga library, and the PostgreSQL PGDG package repository).
RUN apt-get update && apt-get install -y --no-install-recommends \
postgresql-17-pgvector=0.8.6-1.pgdg13+1 \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*