Cannot install Jetstream on my macbook

[MoMa1984]

I tried to install Jetstream on my macbook (macOS 15.2) using Docker but it failed several times.

First I cloned the Rep. and wrote
docker build -t jetstream-app .

After resetting nx as instructed in the error log, it did not work.

[501clouds]

same issue on ubuntu with the dockerfile. I tried setting WORKDIR to / and then /apps to no avail.

After enabling --verbose on the build:core step I get this output:

Require stack:
5.428 - /app/libs/shared/ui-utils/eslint.config.js
5.428 at Module._resolveFilename (node:internal/modules/cjs/loader:1144:15)
5.428 at Module._load (node:internal/modules/cjs/loader:985:27)
5.428 at Module.require (node:internal/modules/cjs/loader:1235:19)
5.428 at require (node:internal/modules/helpers:176:18)
5.428 at Object. (/app/libs/shared/ui-utils/eslint.config.js:2:20)
5.428 at Module._compile (node:internal/modules/cjs/loader:1376:14)
5.428 at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
5.428 at Module.load (node:internal/modules/cjs/loader:1207:32)
5.428 at Module._load (node:internal/modules/cjs/loader:1023:12)
5.428 at cjsLoader (node:internal/modules/esm/translators:345:17)
5.428 Error: Cannot find module '../../../eslint.config.js'

in about 30 different versions with only the path prior to /eslint.config.js changing. I've confirmed I have eslint.config.js in the path under apps and had tried using WORKDIR /apps since the eslint.config.js file appears in that path.

[paustint]

Sorry for the issue, we don't use the Dockerfile internally so it sometimes gets out of date. We will take a look.

You can try checking out tag v4.18.0 and that will most likely work.

Otherwise you can run without using docker and that should work as well.

yarn install
yarn scripts:generate-env
yarn db:migrate
yarn db:seed
yarn build:core
node dist/apps/api/main.js (or in two terminals to run in dev mode: - yarn start and yarn statr:api)

[paustint]

@MoMa1984 @501clouds - you can try out this branch bug/fix-docker and see if that fixes it. It should resolve your immediate issue, but as mentioned in the prior post that it has been a while since docker was tested and there were some big changes in swapping out our authentication code, so it is possible there may be some other issues.