build: up node memory during docker build

[joergkiesewetter]

applying the same change as on #2802, but on main branch

(cherry picked from commit 31e0a4b)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1c5ed43

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[holic]

do you know ENV sticks around in the docker container? as in running the indexer would use 4gb memory too?

[holic]

https://docs.docker.com/reference/dockerfile/#env

The ENV instruction sets the environment variable to the value . This value will be in the environment for all subsequent instructions in the build stage and can be replaced inline in many as well.

sounds like just during build?

[holic]

but also seeing

If an environment variable is only needed during build, and not in the final image, consider setting a value for a single command instead:

so I wonder if we use this instead:

RUN NODE_OPTIONS=--max-old-space-size=4096 pnpm run -r build

[joergkiesewetter]

ok, changed it. For me, the build works like this, as well. I will also do a PR to change it in the "historical_indexer"-branch

[holic]

thanks!