Skip to content

v2.7.3 — Typesense runs as an unprivileged user

Choose a tag to compare

@fmadore fmadore released this 16 Nov 14:43
· 8 commits to main since this release

Upgrading from v2.7.1 or v2.7.2 (only if you run the search profile). Typesense now runs as uid 10002. Hand the existing root-owned volume over once, then start the new image:

git fetch --tags && git checkout v2.7.3
docker compose --profile search build --pull typesense
docker compose stop typesense
docker compose --profile search run --rm --no-deps --user 0 --cap-add CHOWN \
  --entrypoint chown typesense -R 10002:10002 /data
docker compose --profile search up -d typesense

If you skip the chown, Typesense can't write its data directory and won't become healthy. The search index is kept.

Security

  • Typesense runs as an unprivileged user (typesense, 10002:10002) instead of upstream's root. This closes the DS-0002 finding raised against the Dockerfile added in v2.7.2. A fresh typesense_data volume gets the right owner automatically.

v2.7.1 to v2.7.3 cleared every finding from the weekly scan (#60) that has an upstream fix. These are still open:

  • mysql 9.7.4: 3 critical, 33 high and 67 medium, in the Go stdlib and Python packages bundled with the official image. No fixed image has been published yet.
  • ckeditor4 4.20.1 (4 medium): ships with Omeka S core.