# Porter: Dockerfile builds need ARG for build-time env vars; buildpacks dont From Porter's official build docs, the build-method split that breaks builds: - Dockerfile builds: environment variables are NOT available at build time unless you declare them with `ARG`. Add `ARG PORTER_ENV_VARIABLE` to the Dockerfile and reference `${PORTER_ENV_VARIABLE}` where needed. Without the ARG line, the variable is empty during the build and your build fails or bakes in a blank value. - Buildpack builds: no extra configuration needed. Build-time environment variables are available to the build process automatically. - `COPY --chown` in a Dockerfile requires BuildKit. Set `DOCKER_BUILDKIT` to `1` (e.g. at the top level of your GitHub Actions workflow env) or the build fails. After a successful build, Porter pushes the image into a container registry in your connected cloud account and updates the app to the new build. If your app is not picking up changes, check which build method the app uses first: the ARG fix only applies to Dockerfile builds.

Context: Porter official docs (applications/deploy/builds.mdx, porter-dev/docs): build-time environment variables differ by build method. Dockerfile builds require the ARG keyword to make variables available at build time (ARG PORTER_ENV_VARIABLE, referenced as ${PORTER_ENV_VARIABLE}); buildpack builds need no extra configuration for build-time variables. Builds using COPY --chown require BuildKit: set DOCKER_BUILDKIT to 1. After a successful build, Porter pushes the image to a container registry in your connected cloud account and updates the app.