Container Entrypoint Script Loses Runtime Env Vars to Build-Time Substitution
A developer found that a container entrypoint script could not read an environment variable passed at run time, although env inside the same script could. The cause, given in the first reply, is that the script was written via a Dockerfile heredoc, so the variable was expanded during image build and baked in as empty. It matters as a recurring source of confusion where build-time and run-time expansion look identical in source.
Signal
Visibility
Sign in free to unlock the full scoring breakdown, root-cause analysis, and solution blueprint.
Sign up freeAlready have an account? Sign in
Deep Analysis
Root causes, cross-domain patterns, and opportunity mapping
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Solution Blueprint
Tech stack, MVP scope, go-to-market strategy, and competitive landscape
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Similar Problems
surfaced semanticallyQuoted Heredoc Delimiter Silently Strips Environment Variables
A developer using a quoted heredoc delimiter inside a GitHub Actions SSH deploy step finds that referenced environment variables expand to empty strings, while removing the quotes restores expected substitution. The question surfaces a common but poorly understood shell-quoting gotcha affecting secret-passing in CI/CD deploy pipelines.
Prisma Build Secrets Not Passed in Dokploy Next.js Dockerfile
Next.js apps using Prisma at build time fail in Dokploy because DATABASE_URL is not forwarded during the Docker build stage. Developers must hardcode secrets as a workaround. Affects teams adopting Dokploy for self-hosted deployments.
Git Bash Mis-Resolves $USERPROFILE in Docker Volume Mounts on Windows
Developers using Git Bash on Windows to run dotnet dev-certs and mount volumes into Docker find that $USERPROFILE resolves incorrectly, producing a mangled path that breaks container startup, even though the equivalent .bat/cmd.exe script works fine. This path-translation mismatch between Git Bash's POSIX emulation and Windows forces developers to fall back to .bat scripts for Docker-related tasks.
Self-Hosted Coder Workspaces Cannot Access Host Docker Socket or Persist Tooling
A developer self-hosting Coder via Docker Compose cannot get workspace containers to see the mounted host Docker socket for sibling containers, and mise-installed .NET/Node.js tooling does not persist across sessions despite following the documented setup.
Docker containers lose DNS resolution after host reboot due to stale resolv.conf
A long-time Docker user on Debian reports that after a host reboot, containers start successfully but cannot reach the internet because they fail to pick up the host resolv.conf; restarting the containers a few minutes later fixes it. This points to a startup-ordering race between Docker and the host DNS/networking services that surfaces only after a reboot, not during normal operation.
Problem descriptions, scores, analysis, and solution blueprints may be updated as new community data becomes available.