Dockerfile

Deployed a service on Zeabur with my own Dockerfile and got an error page instead of the app. Setting the PORT environment variable did not change anything. The deploy logs showed the app was running and listening, but on a hardcoded port 8

supporting2026-09-23 22:19 UTC

Adding statsig_elixir to a mix project and deploying on a bookworm slim based Dockerfile crashes at startup with Failed to load NIF ... 'libssl.so.1.1: cannot open shared object file'. The prebuilt NIF binary was linked against OpenSSL 1.1,

supporting2026-09-23 22:13 UTC

Renovate fails against a JFrog Artifactory Docker registry with a 406 error when fetching tags, while the same config works against Docker Hub. It runs as a cronjob on OpenShift handling Dockerfiles with pinDigests=true. Two overlapping cau

supporting2026-09-23 21:46 UTC

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

supporting2026-09-23 21:37 UTC

Built a custom Browserless image with the v2 SDK (`npx @browserless.io/browserless create`, then `npm run docker`). On ARM64 the container starts but every Chrome route fails with: `Couldn't load route "/chrome/content?(/)" due to missing b

supporting2026-09-23 12:08 UTC

Submitting a remote build with `gcloud container builds submit --config cloudbuild.yaml`, the .git directory never showed up in the build context even though there was no .dockerignore, no .gitignore, no .gcloudignore, and no "Some files we

supporting2026-09-23 12:05 UTC

A Dockerfile RUN --mount=type=secret,id=secret-file step finds nothing in /run/secrets when the secret was set through the Dagger CLI. The reason: a secret set via the CLI gets its name set to the sha256 checksum of its value, not to any fr

supporting2026-09-23 12:03 UTC

After a node version bump in the CLI's Dockerfile to v12.22.11, codefresh log following broke for pipelines run via the codefresh-pipeline-runner GitHub Action with: Your node version (v12.22.11) is not compatible with supported node versio

incidental2026-09-23 12:03 UTC

Calling start_stream_transcription from a Python 3.7 app inside a Ubuntu 16.04 based Docker container crashed with RuntimeError: 1033 (AWS_IO_TLS_CTX_ERROR): Failed to create tls context. The traceback came from awscrt's io.ClientTlsContext

incidental2026-09-23 12:00 UTC

On Prisma 7, running prisma migrate dev fails with "Error: The datasource property is required in your Prisma config file when using prisma migrate dev", even though prisma.config.ts exists with a datasource url. The reporter had the config

supporting2026-09-23 01:12 UTC