Document non-root container, shared login, and data folder permission fix

- PORTAINER_DEPLOY.md: add the chown step needed after the container
  switched to a non-root user, and note EACCES as the symptom if skipped.
- Update CHANGELOG for the shared login, non-root Dockerfile, and
  cap_drop/no-new-privileges hardening.
This commit is contained in:
2026-09-29 18:03:39 -07:00
parent 0f53a159f0
commit d6e83dcdf5
4 changed files with 30 additions and 2 deletions

View File

@@ -40,16 +40,22 @@ Portainer passes these to Compose as substitution values for the `${VARIABLE_NAM
1. Click **Deploy the stack**.
2. Wait for the build to finish. The image is small; the app has no external dependencies to install.
3. The container now runs as a non-root user (`node`, uid 1000) inside the image, not root. If the `./data` folder on this host already exists from an earlier deploy, it may still be owned by root from when the container ran as root. Fix it once with:
```
sudo chown -R 1000:1000 ./data
```
Run this in the stack's folder on the Docker host (wherever Portainer keeps it for this stack). Skip this if `./data` doesn't exist yet; the container creates it correctly on first run.
## Step 4: Verify
1. Go to **Containers**, find `sde-meeting-toolkit`, and open **Logs**.
2. Confirm the log reports:
- `ANTHROPIC_API_KEY loaded: AI draft button is live.`
- Either `Login required: N named user(s) configured.` or `No login required: ...`, matching what you set in `APP_USERS`.
- Either `Login required: N named user(s) configured.` or `No login required: ...`, matching what you set in `APP_USERS` or `APP_USERNAME`/`APP_PASSWORD`.
- `No per-user token quota: TOKEN_LIMIT_PER_USER is unset or 0 (unlimited, feature on the back burner).`
- No `EACCES` or `permission denied` lines. If you see these, the `chown` step above was skipped or didn't take.
3. Open the container's mapped address in a browser (port `5173` by default, per `docker-compose.yml`). Confirm the toolkit's landing page loads.
4. If you set `APP_USERS`, confirm the browser asks for a login before the page loads.
4. If you set `APP_USERS` or `APP_USERNAME`/`APP_PASSWORD`, confirm the browser asks for a login before the page loads.
5. Try the AI draft button on the Field Problem Workshop tool and confirm it returns a real draft.
## Redeploying after a code change