Docker container for Nextjs without standalone build

[kachar]

Motivation and context

Recently we've introduced frontend docker image with standalone builds, but they are not stable enough and do not provide all the needed features so the app runs smoothly.

The feature that we miss the most is reading having publicRuntimeConfig function to read the secrets from the environment (process.env). With standalone builds, the environment is being read only at build time and it brings hardcoded values to the runtime config. (link)

With this PR we roll back the change.

The docker image size in standalone mode is 263MB which was awesome, now we're back at 950+MB bringing all the node_module/ and .next folders to the final production image.

Another downside of standalone approach is that it's not yet compatible with Next 13 and app directory structure.

We're following the progress in the main Nextjs repo around these topic

• Standalone output does not load runtimeConfig from environment variables vercel/next.js#38119
• NEXT_PUBLIC Environment Variables not avaliable on Client in Standalone vercel/next.js#37537
• outputStandalone + serverRuntimeConfig not working as expected vercel/next.js#33910 (comment)
• Allow dynamic `serverRuntimeConfig` and `publicRuntimeConfig` values from `process.env.*` with `outputStandalone: true` vercel/next.js#34894