Your Dockerfile builds, your container starts, and your triggers never fire. The Functions host logs "no functions found" or the container sits idle, processing nothing. The gap between a working image and a working function app is entirely configuration. The runtime needs specific environment variables, the build must publish to the exact path the host expects, and Azurite connections behave differently inside a container network than on localhost. Four walls, four fixes. All code samples are in the companion repo . Pitfall 1: Environment Variables That Vanish Your container starts, the Functions host initializes, and the logs show this: [2026-04-20T08:12:03Z] No job functions found. Try making your job classes and methods public. [2026-04-20T08:12:03Z] If you're using binding extensions (e.g.…