platform · inferred from evidence
Docker
A container platform referenced in the context of Traefik middleware configurations.
- TeamCity agent docker-in-docker: x509 certificate signed by unknown authority on private registry
The certificate volume was not actually mounted inside the agent container, so Docker inside the agent never saw the CA. Create the CA certificate directly in the container at /etc/docker/certs.d/[mydomain.com]/ca.crt (per the teamcity-mini
- Lago one-click Docker: 'An error occured, please restart the application' when adding Stripe integration
The 500 came from Lago's Segment analytics call, not from Stripe. Workaround confirmed by the reporter: disable Segment by adding `-e LAGO_DISABLE_SEGMENT="true"` to the docker run command — the Segment error disappears after that. The main
- TimescaleDB Docker upgrade: could not access file "$libdir/timescaledb-X.Y.Z"
Run `ALTER EXTENSION timescaledb UPDATE;` in every database where TimescaleDB is installed, including the `postgres` database, which people often forget (sometimes even `template0` needs it). If you are jumping several versions at once, do
- Steel Browser docker compose fails on second run: Xvfb Fatal server error, Server is already active for...
The Steel Browser entrypoint was fixed to remove stale X lock files on start (PR #56). Pull the latest image and rebuild with `docker-compose up --force-recreate --build` so the fixed entrypoint takes effect. As a one-off workaround on an a
- Semgrep cannot invoke on ARM aarch64 Android Termux
Semgrep now ships ARM support: multi-arch Docker images (linux/amd64 + linux/arm64) since 1.31.2, aarch64 Python wheels on PyPI since 1.33.1, and musllinux (Alpine) aarch64 wheels since 1.38.0. Upgrade to 1.38.0 or later on ARM, for Docker
- KServe deployment fails when using a cloud shared disk as PV even with model files already present
If your KServe NIM deployment keeps trying to download models and fails despite the files being on the PV, the NIM cache was never initialized where KServe expects it. First run the NIM once outside KServe, as a docker command or a K8s Job
- LoRAX: TensorParallelHead object has no attribute base_layer when serving Mixtral with an adapter
This crash is a LoRAX bug in adapter loading for Mixtral's tensor-parallel head, fixed in PR #131. Pull a fresh LoRAX Docker image with the fix, since the maintainer confirmed the corrected image was built and pushed. If you pinned an image
- Cannot find module '@prisma/client/runtime/query_compiler_bg.postgresql.wasm' (MODULE_NOT_FOUND)
First check for a version mismatch: npx prisma --version and make sure prisma and @prisma/client are on the same version; several reporters fixed it by upgrading both packages to the same release (e.g. both to 7.3.0). If versions match, che