Fix .gitignore for Files Already Tracked in Git Repos
Updated: Oct 07, 2025
Overview Symptom: you add patterns to .gitignore, but Git still shows changes for files you expected to be ignored. Root cause: .gitignore only affects untracked files. Anything already in the index remains tracked until explicitly removed......
Fix Git LF/CRLF warnings with .gitattributes and autocrlf
Updated: Oct 07, 2025
What these warnings mean Git is telling you it will convert line endings between LF (Unix) and CRLF (Windows) based on your settings or attributes: warning: LF will be replaced by CRLF warning: CRLF will be replaced by LF These appear......
Fix Docker builds that reuse cache unexpectedly or ignore --no-cache
Updated: Oct 06, 2025
Overview Docker build caching is powerful but can surprise you: layers appear as cached when you expected fresh work, or --no-cache seems ignored. This guide shows how to diagnose, force clean builds, and structure Dockerfiles to avoid......
Fix Docker 'copy file range failed: invalid argument' on Windows
Updated: Oct 06, 2025
Overview On Windows (especially with Docker Desktop using WSL2), docker build, docker cp, or buildx outputs may fail with: failed to copy files: copy file range failed: invalid argument Root cause: the optimized copy syscall......
Fix /bin/sh^M: bad interpreter in Docker containers
Updated: Oct 06, 2025
Overview The error /bin/sh^M: bad interpreter in a Linux container means the script file has Windows (CRLF) line endings. Linux expects LF. The extra carriage return (^M) in the shebang (#!/bin/sh) prevents the kernel from finding the......
Fix 'User specified in Dockerfile does not exist' at runtime
Updated: Oct 06, 2025
Overview Docker fails to start a container when the USER declared in the Dockerfile (or passed with --user) is not present in the final image. Typical causes: The base image lacks that user/group. You created the user in a builder stage......
Fix OCI runtime exec failed: bash not found in PATH (Docker)
Updated: Oct 06, 2025
What this error means You ran a command like: docker exec -it <container> bash and got: OCI runtime exec failed: exec: "bash": executable file not found in $PATH This means the container does not have bash installed, or......
Fixing “OCI runtime exec failed: container not running” in Docker
Updated: Oct 06, 2025
Overview When docker exec returns: OCI runtime exec failed: container not running it means Docker found the container object, but its state is not running (it may be exited, dead, created, or paused). The fix is to start or unpause the......
Fixing “OCI runtime create failed” when starting Docker containers
Updated: Oct 06, 2025
Overview The error “OCI runtime create failed: runc create failed: unable to start container process” is a wrapper around a more specific cause. The key is to read the trailing part of the message and then verify image entrypoints,......
How to fix 'OCI runtime create failed: permission denied' in Docker
Updated: Oct 06, 2025
What this error means The error “OCI runtime create failed: permission denied” occurs when the container runtime (runc/containerd via Docker) cannot start the container due to a host-level access control denial. Common......
Fix Docker 'no such file or directory' (CRLF, shebang)
Updated: Oct 06, 2025
Overview In Docker, the message "exec user process caused: no such file or directory" usually appears when the container tries to exec your entrypoint or CMD and the kernel cannot run it. The most common causes are: CRLF line......
Fix Docker 'executor failed running [/bin/sh -c …]: exit 127'
Updated: Oct 06, 2025
What the error means Exit code 127 in Docker builds means command not found. During a RUN step, Docker executes your command with /bin/sh -c (unless you use exec form). If the command or interpreter is missing, or the path is wrong, you......