Free, Open Source, Self-Hosted WhatsApp API Gateway
TypeScript apibotgatewayself-hostedwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-gatewaywhatsapp-gateway-apiwhatsapp-webwhatsapp-web-api
fix(docker): replace the withdrawn minio/minio image with pgsty/silo
Yudhi Armyndharis264534057133
diff --git a/.github/dependabot.yml b/.github/dependabot.ymlindex d5d7c3703..f810eb1cc 100644--- a/.github/dependabot.yml+++ b/.github/dependabot.yml@@ -170,10 +170,11 @@ updates:- dependency-name: "node"update-types: ["version-update:semver-major"]- # The compose stack's pinned images (docker-compose.yml): socket-proxy, postgres, redis, minio.- # A postgres, redis or minio bump fails src/modules/docker/compose-parity.spec.ts until the same- # tag is set in src/modules/docker/docker.service.ts; that failure is intended, so edit both on- # the Dependabot branch. tecnativa/docker-socket-proxy has no such mirror and no CI gate on its+ # The compose stack's pinned images (docker-compose.yml): socket-proxy, postgres, redis, and+ # pgsty/silo for the `minio` service. A postgres, redis or silo bump fails+ # src/modules/docker/compose-parity.spec.ts until the same image reference (for silo, tag and+ # digest) is set in src/modules/docker/docker.service.ts; that failure is intended, so edit both+ # on the Dependabot branch. tecnativa/docker-socket-proxy has no such mirror and no CI gate on its# behaviour: review its release notes against the allow-list in docker-compose.yml and re-run# scripts/smoke-test-docker-proxy.sh by hand before merging one.- package-ecosystem: docker-compose@@ -195,5 +196,3 @@ updates:# (ci.yml, release.yml), which no ecosystem updates. A deliberate, by-hand move.- dependency-name: "redis"update-types: ["version-update:semver-major"]- # Being replaced (#1729), and the registry no longer serves the image.- - dependency-name: "minio/minio"diff --git a/README.md b/README.mdindex 97fe268df..fc2f00ce6 100644--- a/README.md+++ b/README.md@@ -270,12 +270,12 @@ docker compose --profile postgres up -ddocker compose --profile full up -d```-| Profile | Services |-| ---------- | --------------------- |-| `postgres` | PostgreSQL database |-| `redis` | Redis cache |-| `minio` | S3-compatible storage |-| `full` | All services above |+| Profile | Services |+| ---------- | ----------------------------------------------- |+| `postgres` | PostgreSQL database |+| `redis` | Redis cache |+| `minio` | S3-compatible storage (MinIO fork `pgsty/silo`) |+| `full` | All services above |A profile only starts the container; OpenWA keeps using SQLite and local storage until it is toldto use the new service. The simplest route is **Dashboard > Infrastructure**: pick the built-indiff --git a/docker-compose.yml b/docker-compose.ymlindex e8ab4d51e..5e87e09ed 100644--- a/docker-compose.yml+++ b/docker-compose.yml@@ -483,9 +483,12 @@ services:- 'com.openwa.service=cache'- 'com.openwa.builtin=true'- # ===== OPTIONAL: Built-in MinIO (S3-compatible) =====+ # ===== OPTIONAL: Built-in S3-compatible storage (pgsty/silo, a maintained MinIO fork) =====+ # Pinned by release tag and digest. Same server command, MINIO_ROOT_* variables, /data layout and+ # health route as MinIO, so an existing openwa_minio-data volume is used as-is. The service,+ # container and host name stay `minio`.minio:- image: minio/minio:RELEASE.2025-09-07T16-13-09Z+ image: pgsty/silo:RELEASE.2026-09-16T00-00-00Z@sha256:635197cb9f36d01bee221d34d1c7d7960f6a95c48b0b6c01d99cd13bdae51a46container_name: openwa-minioprofiles: ['minio', 'full']restart: unless-stoppeddiff --git a/docs/14-migration-guide.md b/docs/14-migration-guide.mdindex a330c10ba..0ae038b5c 100644--- a/docs/14-migration-guide.md+++ b/docs/14-migration-guide.md@@ -251,6 +251,20 @@ curl -X POST 'http://localhost:2785/api/infra/storage/import' \| Built-in MinIO → External S3 | ✅ | Export → Config → Import || S3 → Local | ✅ | Export → Config → Import |+The built-in storage (the compose `minio` profile and the dashboard's built-in option) runs+`pgsty/silo`, a maintained MinIO fork, on the same `openwa_minio-data` volume. An `openwa-minio`+container created from the older `minio/minio` image keeps running it until it is recreated: on the+compose route run `docker compose --profile minio pull minio && docker compose --profile minio up -d minio`;+for the dashboard built-in run `docker rm -f openwa-minio`, then restart OpenWA or re-save the+built-in storage. The recreated dashboard built-in container publishes no host ports: the older one+published the S3 API and console on `127.0.0.1:9000` and `127.0.0.1:9001`, and OpenWA reaches the new+one over the Docker network alone. For host access to either, run storage through the compose `minio`+profile, which still publishes both on loopback. The compose `minio` service no longer starts without `S3_ACCESS_KEY_ID` and+`S3_SECRET_ACCESS_KEY` in the `.env` next to `docker-compose.yml`: a container that ran with neither+set used `minioadmin`/`minioadmin`, so set them to the pair OpenWA uses before recreating it. If+OpenWA uses the dashboard built-in storage, drop the `minio`/`full` profile and take the dashboard+route instead. The volume and its media are kept either way.+### Redis Migration (Cache)Redis in OpenWA holds only **ephemeral** state: TTL-based cache entries, BullMQ jobs (see below), and — when `REDIS_ENABLED` — the rate-limit hit counters. Cache data automatically regenerates from the database.diff --git a/docs/16-risk-management.md b/docs/16-risk-management.mdindex 4e69aeae6..3b3c0af96 100644--- a/docs/16-risk-management.md+++ b/docs/16-risk-management.md@@ -312,7 +312,7 @@ Dependencies (`whatsapp-web.js`, Puppeteer, NestJS, etc.) may have vulnerabiliti**Mitigation Strategies:**-> **Current state:** the real dependency check is a dedicated `audit` job in `ci.yml` running `npm run check:audit` over the root tree and `npm audit --audit-level=high` over `dashboard/` (on push and PR); it is deliberately split out of the `Lint` job so a newly published advisory cannot abort the other quality gates. `check:audit` keeps the `high` threshold but applies it per advisory, so one with no patched version can be excused by id in `scripts/check-audit.mjs` — with its reason and removal condition recorded, and a stale entry failing the job — instead of lowering the bar for everything. `release.yml` repeats both and additionally runs a Trivy image scan (`CRITICAL,HIGH`, `ignore-unfixed`) against an explicit `.trivyignore` before the release tags are promoted. Dependabot PRs cover npm for `/` and `/dashboard` (weekly), GitHub Actions (monthly), the Dockerfile base image and the `docker-compose.yml` images (weekly; PostgreSQL and Redis majors and MinIO ignored), with version-pinned ignores (seven in the root tree, two in `/dashboard`) whose reasons and lift conditions are recorded in `.github/dependabot.yml`. Between releases, `.github/workflows/security-scan.yml` (Scheduled Security Scan) runs every Wednesday at 03:00 UTC and on demand: it repeats the `audit` job and the release Trivy scan against the published `latest` image on amd64 and arm64, so an advisory those gates would block fails a run within a week of being published; the amd64 Chrome for Testing binary stays outside what Trivy can see (see `.trivyignore`). Its `base-image-drift` job fails when the Dockerfile's two `node:22-slim` FROM digests disagree, or when the pin differs from what the tag serves today and either the tag has served that image for 7 or more days, or for 3 or more days with the pin last changed 28 or more days ago; it backstops a Dependabot digest refresh that is late or left unmerged. There is **no** Snyk integration. The workflow below is a recommended enhancement to add Snyk; its scheduled `npm audit` is already covered by `security-scan.yml`.+> **Current state:** the real dependency check is a dedicated `audit` job in `ci.yml` running `npm run check:audit` over the root tree and `npm audit --audit-level=high` over `dashboard/` (on push and PR); it is deliberately split out of the `Lint` job so a newly published advisory cannot abort the other quality gates. `check:audit` keeps the `high` threshold but applies it per advisory, so one with no patched version can be excused by id in `scripts/check-audit.mjs` (with its reason and removal condition recorded, and a stale entry failing the job) instead of lowering the bar for everything. `release.yml` repeats both and additionally runs a Trivy image scan (`CRITICAL,HIGH`, `ignore-unfixed`) against an explicit `.trivyignore` before the release tags are promoted. Dependabot PRs cover npm for `/` and `/dashboard` (weekly), GitHub Actions (monthly), the Dockerfile base image and the `docker-compose.yml` images (weekly; PostgreSQL and Redis majors ignored, and a postgres, redis or pgsty/silo bump fails `compose-parity.spec.ts` until `src/modules/docker/docker.service.ts` carries the same image reference), with version-pinned ignores (seven in the root tree, two in `/dashboard`) whose reasons and lift conditions are recorded in `.github/dependabot.yml`. Between releases, `.github/workflows/security-scan.yml` (Scheduled Security Scan) runs every Wednesday at 03:00 UTC and on demand: it repeats the `audit` job and the release Trivy scan against the published `latest` image on amd64 and arm64, so an advisory those gates would block fails a run within a week of being published; the amd64 Chrome for Testing binary stays outside what Trivy can see (see `.trivyignore`). Its `base-image-drift` job fails when the Dockerfile's two `node:22-slim` FROM digests disagree, or when the pin differs from what the tag serves today and either the tag has served that image for 7 or more days, or for 3 or more days with the pin last changed 28 or more days ago; it backstops a Dependabot digest refresh that is late or left unmerged. There is **no** Snyk integration. The workflow below is a recommended enhancement to add Snyk; its scheduled `npm audit` is already covered by `security-scan.yml`.```yaml# .github/workflows/security.ymldiff --git a/src/modules/docker/compose-parity.spec.ts b/src/modules/docker/compose-parity.spec.tsindex c9af8bbc0..8d54911c1 100644--- a/src/modules/docker/compose-parity.spec.ts+++ b/src/modules/docker/compose-parity.spec.ts@@ -143,9 +143,17 @@ describe('DockerService managed specs ↔ docker-compose.yml parity', () => {const cfg = await capture(profile);expect(cfg.Image).toBe(compose.services[profile].image);expect(cfg.Image).toContain(':'); // an explicit tag, never the floating default+ expect(cfg.Image).not.toMatch(/:latest(@|$)/);expect(cfg.name).toBe(compose.services[profile].container_name);});+ it('minio: pins a release tag and an image digest, and not the withdrawn minio/minio image', async () => {+ // The equality above keeps both sides the same; this keeps the digest from being dropped from both.+ const cfg = await capture('minio');+ expect(cfg.Image).toMatch(/:RELEASE\.[0-9T-]+Z@sha256:[0-9a-f]{64}$/);+ expect(cfg.Image).not.toMatch(/^(quay\.io\/)?minio\/minio[:@]/);+ });+it.each(PROFILES)('%s: attaches to the fixed openwa-network like the compose service', async profile => {const cfg = await capture(profile);expect(cfg.HostConfig.NetworkMode).toBe('openwa-network');diff --git a/src/modules/docker/docker.service.ts b/src/modules/docker/docker.service.tsindex ccc4a4cb5..d61efa8a9 100644--- a/src/modules/docker/docker.service.ts+++ b/src/modules/docker/docker.service.ts@@ -300,8 +300,9 @@ export class DockerService implements OnModuleInit {securityOpt: ['no-new-privileges:true'],},minio: {- // Same pin as the compose minio service — never track the floating `latest` tag.- image: 'minio/minio:RELEASE.2025-09-07T16-13-09Z',+ // Same pin (release tag and digest) as the compose minio service; never a floating tag.+ image:+ 'pgsty/silo:RELEASE.2026-09-16T00-00-00Z@sha256:635197cb9f36d01bee221d34d1c7d7960f6a95c48b0b6c01d99cd13bdae51a46',name: 'openwa-minio',alias: 'minio',cmd: ['server', '/data', '--console-address', ':9001'],