platform · inferred from evidence
Docker
A container platform referenced in the context of Traefik middleware configurations.
- Can't reach the local install page after deploying Dify with Docker (nginx restarting)
After deploying Dify with Docker, the web container kept restarting and the local install page never loaded. The nginx container logs showed emerg bind() to the all-interfaces address on port 80 failed (98: Address already in use). Somethin
- fake-gcs-server returns 500 when started with an empty mounted data directory
Running fake-gcs-server in Docker with a data volume mounted to an initially empty directory failed. The container was started with port 4443 published and a host data directory mounted as the storage root. Querying the local storage API ov
- TaskingAI fails to start with ConnectionRefusedError on port 8002
When I started the TaskingAI app, I got a ConnectionRefusedError with Errno 10061 Connect call failed (loopback, 8002). I was running the code directly, not via Docker. The maintainer asked for a docker ps screenshot and then gave the answe
- Qdrant docker "jemalloc: Unsupported system page size" on aarch64, Aborted (core dumped)
Starting qdrant/qdrant:v1.9.2 with docker run on an arm64 cloud machine (Kunpeng920 CPU) aborted on startup: "[jemalloc]: Unsupported system page size [jemalloc]: Unsupported system page size memory allocation of 5 bytes failed" followed by
- Meilisearch Docker v0.24: data.ms volume mount empty (data dir moved to the meili user home)
With Meilisearch v0.24 in Docker, mounting a persistence volume with `-v $(pwd)/data.ms:/data.ms` left the host folder empty: no data was persisted. The docs still said Meilisearch writes to `/data.ms`, but after the Docker user change, the
- Wrong port in redirect_uri with Docker port mapping (FusionAuth 1.37+, fixed in 1.46.0)
Running FusionAuth in Docker with a port mapping like 2222:9011, the Identity Provider login redirect_uri contained the wrong (internal) port from FusionAuth 1.37 through 1.45.x, so the IdP callback went to an unreachable URL and login fail
- TeamCity agent docker-in-docker: x509 certificate signed by unknown authority on private registry
Running a TeamCity build agent with Docker-in-Docker, pushing to a private company registry with a valid certificate failed with: x509: certificate signed by unknown authority. Mounting a volume at /etc/docker/certs.d/[mydomain.com]/ca.crt
- LoRAX: No local weights error when loading an adapter from a local directory
Loading a local LoRA adapter failed with `GenerationError: Request failed during generation: Server error: No local weights...` even though the directory contained adapter_config.json and adapter_model.bin. Maintainer tgaddair spotted the r
- UI errors loading traces after Langfuse upgrade: corrupted ClickHouse parts
After upgrading the self-hosted Langfuse docker image, the UI throws internal errors loading traces and traces are unreachable: logs show ClickHouse `Stream String.size for column project_id/trace_id with type String is not found` and `Ther
- Lago one-click Docker: 'An error occured, please restart the application' when adding Stripe integration
Running Lago's single Docker image (v1.25.0 and 1.24.1) via `docker run --rm -it --name lago -p 80:80 -p 3000:3000 getlago/lago:v1.25.0`, clicking Integrations > Stripe and entering a Stripe test secret key produced the UI toast 'An error o
- Firebolt Core crashes on Alpine: "Database catalog is initialized twice"
Starting the Firebolt Core Docker image on Alpine Linux crashed immediately with `Terminating with uncaught exception: Code: 49, e.displayText() = Database catalog is initialized twice. This is a bug.` The reporter was mounting a data volum
- TimescaleDB Docker upgrade: could not access file "$libdir/timescaledb-X.Y.Z"
After upgrading the TimescaleDB Docker image, every query fails with `ERROR: could not access file "$libdir/timescaledb-1.4.0": No such file or directory`, even after `ALTER EXTENSION timescaledb UPDATE;` says the extension is up to date. T
- Steel Browser docker compose fails on second run: Xvfb Fatal server error, Server is already active for...
Running Steel Browser's docker compose a second time kills the API with: `(EE) Fatal server error: Server is already active for display 10 - If this server is no longer running, remove /tmp/.X10-lock and start again.` Xvfb cant start becaus
- Semgrep cannot invoke on ARM aarch64 Android Termux
Semgrep installs on ARM (e.g. an Android tablet via Termux, or aarch64 Linux) but cannot be invoked, the bundled OCaml binary is x86-64 only, so it fails on ARM systems.
- KServe deployment fails when using a cloud shared disk as PV even with model files already present
Following the KServe deployment steps with an Alibaba Cloud shared disk as the persistent volume, the NIM kept trying to download model files and errored out even though the files were already in the directory. The traceback died in `inject
- MinIO: anonymous PUT to public bucket with AWS SDK Java v2.30 fails with 400 "Missing fields in request"
Running MinIO locally in Docker with a public bucket, an anonymous PUT with the AWS SDK for Java v2 (2.30.x) fails with: software.amazon.awssdk.services.s3.model.S3Exception: Missing fields in request. (Service: S3, Status Code: 400). The t
- LoRAX: TensorParallelHead object has no attribute base_layer when serving Mixtral with an adapter
Starting LoRAX with `mistralai/Mixtral-8x7B-Instruct-v0.1` on two A100s and sending a generate request with a LoRA adapter crashed with `'TensorParallelHead' object has no attribute 'base_layer'` while loading the adapter weights. Maintaine
- n8n "Extract from File" node with "Extract From PDF" kills the container with exit code 132
I am self-hosting n8n 1.110.1 in Docker (Ubuntu 24.04, Node 22). My workflow uploads a PDF through a Form node and passes it to the "Extract from File" node set to "Extract From PDF". When I execute it, the whole n8n container dies and rest
- Repeated "New timer generated is less than read level" in Temporal history logs
After adding a second node to a freshly bootstrapped one-node Temporal cluster, the history service logs "New timer generated is less than read level" once per second, indefinitely, on the original node. The cluster otherwise works. Tempora
- Zyte headless proxy docker build fails: incorrect CA certificate checksum
Building the zyte-smartproxy-headless-proxy docker image fails with an incorrect CA certificate checksum. The Dockerfile downloads Zyte's proxy CA certificate to intercept HTTPS traffic, but the download link/checksum it ships is stale, so