container: use fixed PGroonga version

This commit is contained in:
naskya 2024-03-19 01:21:01 +09:00
parent a5c4b8b56d
commit 09d51cf838
No known key found for this signature in database
GPG key ID: 712D413B3A9FED5C
2 changed files with 4 additions and 4 deletions

View file

@ -52,7 +52,7 @@ services:
db:
restart: unless-stopped
image: docker.io/groonga/pgroonga:latest-alpine-16-slim
image: docker.io/groonga/pgroonga:3.1.8-alpine-16-slim
container_name: firefish_db
networks:
- calcnet

View file

@ -74,14 +74,14 @@ db:
Please edit your `docker-compose.yml` to replace the database container image from `docker.io/postgres` to `docker.io/groonga/pgroonga`.
Please make sure to use the same PostgreSQL version. If you are using `docker.io/postgres:16-alpine` (PostgreSQL v16), the corresponding image tag is `docker.io/groonga/pgroonga:latest-alpine-16` (or `docker.io/groonga/pgroonga:latest-alpine-16-slim`).
The list of tags can be found on <https://hub.docker.com/r/groonga/pgroonga/tags>. Tags are named as `{PGroonga version}-{alpine or debian}-{PostgreSQL major version}`.
The list of tags can be found on <https://hub.docker.com/r/groonga/pgroonga/tags>.
Please make sure to use the same PostgreSQL version. If you are using `docker.io/postgres:16-alpine` (PostgreSQL v16), the corresponding image is `docker.io/groonga/pgroonga:3.1.8-alpine-16` (or `docker.io/groonga/pgroonga:3.1.8-alpine-16-slim`). There are also tags called `latest-alpine-16` and `latest-alpine-16-slim`, but please be careful if you use these tags since [PGroonga may introduce breaking changes](https://pgroonga.github.io/upgrade/), similar to PostgreSQL.
```yaml
db:
restart: unless-stopped
image: docker.io/groonga/pgroonga:latest-alpine-16-slim # change here
image: docker.io/groonga/pgroonga:3.1.8-alpine-16-slim # change here
container_name: firefish_db
```