docker: Error response from daemon: OCI runtime create failed

OCI runtime errors increased significantly after 2021 due to widespread adoption of Apple Silicon (arm64) Macs. When you docker pull or docker build on an M1/M2/M3 Mac without specifying --platform, Docker uses the host platform (linux/arm64). Images built for arm64 fail on amd64 servers with an OCI runtime error — typically "exec format error" — because the container binary was compiled for a different CPU architecture. The architecture mismatch goes undetected locally because Docker Desktop on macOS uses Rosetta 2 emulation to run amd64 images on arm64 transparently. The image appears to work locally, then fails in production on x86-64 servers. Docker BuildKit's multi-platform builds are the production solution: docker buildx build --platform linux/amd64,linux/arm64 -t myimage:latest --push . creates a multi-architecture manifest. When deployed, Docker automatically pulls the matching variant for the host architecture. For CI/CD pipelines, building on an x64 GitHub Actions runner (ubuntu-latest) with --platform linux/amd64 ensures the image matches x64 production even when developers test on Apple Silicon. OCI runtime errors in containerized Lambda functions trace to this same mismatch — Lambda supports both x86_64 and arm64, and the Architecture property in your Lambda config must match the Docker image's target platform exactly.