Having this issue at the moment. Have you found a workaround?

I have not, unfortunately. In my case, I luckily could get by with using just .env

Yes I did the same on before build i copy files to .env and temp delete the other files. This is also a affects .env.test.

With this answer I was able to access my environment variable inside my docker container.

What I did:

Add my environment variables as docker build arg

docker build --build-arg API_URL_1=https://... -t nextjs-standalone-envvar-bug:latest .

Define ENV variable in Dockerfile

ARG API_URL_1
ENV API_URL_1 = ${API_URL_1}

Use global.process.env instead of process.env

global.process.env.API_URL_1

I have experienced this issue - public variables from .env.local are inlined into the build perfectly fine, but the server-side variables are missing from the resultant .env file which is bundled with the build.

The workaround I've found is to simply copy the .env.local file to the build folder. In the case of your repo, copying to the app folder of the runner stage in Dockerfile (this is how mine is set up too). It seems like env files are still picked up by a build at run time.

I'm also having this issue. .env and .env.production are copied to .next/standalone, but .env.local is missing.

Hey all, same for .env.test

I ran into the same issue with my GitHub Actions CI. I've created the env file in the CI itself:

 - name: "Create frontend env file"
   run: |
        touch apps/web/.env
        echo NEXT_PUBLIC_ENV1=${{ secrets.NEXT_PUBLIC_ENV1 }} >> apps/web/.env
        echo NEXT_PUBLIC_ENV2=${{ secrets.NEXT_PUBLIC_ENV2 }} >> apps/web/.env

This is still an issue in 2024. If you do not precede all of the variables names with NEXT_PUBLIC the variables will not be available on the server. This leaves the SSR feature of storing secrets on the Next.js server completely unusable. This must be fixed as soon as possible.

It is important to notice that this is an issue not only for environment variables defined in the .env file, but also for environment variables that are passed to next build command.

Doing:

MY_VARIABLE=my-variable-value next build

Does not work neither, using process.env.MY_VARIABLE server side will always give undefined.