starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #3005] [bug]: Cant't compose Hoppscotch app on remote #976

New issue

Closed

opened 2026-03-16 17:54:48 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 17:54:48 +03:00

Owner

Originally created by @fabbow on GitHub (Apr 19, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3005

Is there an existing issue for this?

I have searched the existing issues

Current behavior

I can build the Hoppscotch app on my machine as per the self-hosting docs without issues.

When I run docker compose up within a remote context, the admin, backend and database services build just fine, but the app build exits like this:

[+] Building 135.2s (13/16)                                                                                    
 => [internal] load .dockerignore                                                                         0.7s
 => => transferring context: 2B                                                                           0.1s
 => [internal] load build definition from Dockerfile                                                      0.7s
 => => transferring dockerfile: 517B                                                                      0.1s
 => [internal] load metadata for docker.io/library/caddy:2-alpine                                         0.4s
 => [internal] load metadata for docker.io/library/node:lts                                               0.4s
 => [builder 1/7] FROM docker.io/library/node:lts@sha256:671ee8d49ce2a691fc3082203c5deb9522e0c80042aa0ff  0.0s
 => [internal] load build context                                                                        15.5s
 => => transferring context: 17.34MB                                                                     13.1s
 => [stage-1 1/4] FROM docker.io/library/caddy:2-alpine@sha256:eefd3d61e9ee8f35e046f614982d9a970006e3943  0.0s
 => CACHED [builder 2/7] WORKDIR /usr/src/app                                                             0.0s
 => CACHED [builder 3/7] RUN npm i -g pnpm                                                                0.0s
 => CACHED [builder 4/7] COPY . .                                                                         0.0s
 => CACHED [builder 5/7] RUN pnpm install                                                                 0.0s
 => CACHED [builder 6/7] WORKDIR /usr/src/app/packages/hoppscotch-selfhost-web/                           0.0s
 => ERROR [builder 7/7] RUN pnpm run build                                                              118.4s
------
 > [builder 7/7] RUN pnpm run build:
#0 1.767 
#0 1.767 > @hoppscotch/selfhost-web@2023.4.0 build /usr/src/app/packages/hoppscotch-selfhost-web
#0 1.767 > node --max_old_space_size=16384 ./node_modules/vite/bin/vite.js build
#0 1.767 
#0 5.657 vite v3.2.4 building for production...
#0 5.885 transforming...
#0 27.35 transforming...
#0 27.37 ✓ 1 modules transformed.
#0 27.42 rendering chunks...
#0 65.08 Use of eval is strongly discouraged, as it poses security risks and may cause issues with minification
#0 93.34 ✓ 5545 modules transformed.
#0 117.4 Killed
#0 117.9  ELIFECYCLE  Command failed with exit code 137.

Steps to reproduce

Clone Repo
Install Dependencies
Add remote context via ssh connection
Run docker compose up on the remote

Environment

Production

Version

Self-hosted

Originally created by @fabbow on GitHub (Apr 19, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3005 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior I can build the Hoppscotch app on my machine as per the self-hosting docs without issues. When I run `docker compose up` within a remote context, the admin, backend and database services build just fine, but the app build exits like this: ``` [+] Building 135.2s (13/16) => [internal] load .dockerignore 0.7s => => transferring context: 2B 0.1s => [internal] load build definition from Dockerfile 0.7s => => transferring dockerfile: 517B 0.1s => [internal] load metadata for docker.io/library/caddy:2-alpine 0.4s => [internal] load metadata for docker.io/library/node:lts 0.4s => [builder 1/7] FROM docker.io/library/node:lts@sha256:671ee8d49ce2a691fc3082203c5deb9522e0c80042aa0ff 0.0s => [internal] load build context 15.5s => => transferring context: 17.34MB 13.1s => [stage-1 1/4] FROM docker.io/library/caddy:2-alpine@sha256:eefd3d61e9ee8f35e046f614982d9a970006e3943 0.0s => CACHED [builder 2/7] WORKDIR /usr/src/app 0.0s => CACHED [builder 3/7] RUN npm i -g pnpm 0.0s => CACHED [builder 4/7] COPY . . 0.0s => CACHED [builder 5/7] RUN pnpm install 0.0s => CACHED [builder 6/7] WORKDIR /usr/src/app/packages/hoppscotch-selfhost-web/ 0.0s => ERROR [builder 7/7] RUN pnpm run build 118.4s ------ > [builder 7/7] RUN pnpm run build: #0 1.767 #0 1.767 > @hoppscotch/selfhost-web@2023.4.0 build /usr/src/app/packages/hoppscotch-selfhost-web #0 1.767 > node --max_old_space_size=16384 ./node_modules/vite/bin/vite.js build #0 1.767 #0 5.657 vite v3.2.4 building for production... #0 5.885 transforming... #0 27.35 transforming... #0 27.37 ✓ 1 modules transformed. #0 27.42 rendering chunks... #0 65.08 Use of eval is strongly discouraged, as it poses security risks and may cause issues with minification #0 93.34 ✓ 5545 modules transformed. #0 117.4 Killed #0 117.9 ELIFECYCLE Command failed with exit code 137. ``` ### Steps to reproduce 1. Clone Repo 2. Install Dependencies 3. Add remote context via ssh connection 4. Run `docker compose up` on the remote ### Environment Production ### Version Self-hosted

kerem

2026-03-16 17:54:48 +03:00

closed this issue
added the
bug

need testing

self-host
labels

kerem commented

2026-03-16 17:55:05 +03:00

Author

Owner

@fabbow commented on GitHub (Apr 19, 2023):

Upon a bit of further reading, that does look like a RAM issue due to building on a remote. I assume the solution is to either beef up the machine or build locally and push the images to a registry for now :)

@fabbow commented on GitHub (Apr 19, 2023): Upon a bit of further reading, that does look like a RAM issue due to building on a remote. I assume the solution is to either beef up the machine or build locally and push the images to a registry for now :)

kerem commented

2026-03-16 17:55:10 +03:00

Author

Owner

@eljump commented on GitHub (Apr 25, 2023):

I found this line in the configuration:

node --max_old_space_size=16384

However, in your Docker configuration, it says that 2GB is enough, and that's why you are getting the error 137. The VPS has less RAM than is allowed to be used.

@eljump commented on GitHub (Apr 25, 2023): I found this line in the configuration: ``` node --max_old_space_size=16384 ``` However, in your Docker configuration, it says that 2GB is enough, and that's why you are getting the error 137. The VPS has less RAM than is allowed to be used.

kerem commented

2026-03-16 17:55:15 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 25, 2023):

I've updated the documentation site to make more clarity on the system requirements while building the image and hosting the built output files. Thanks for noticing the lack of clarity in the docs.

@liyasthomas commented on GitHub (Apr 25, 2023): I've updated the documentation site to make more clarity on the system requirements while building the image and hosting the built output files. Thanks for noticing the lack of clarity in the docs.

kerem commented

2026-03-16 17:55:20 +03:00

Author

Owner

@NicklasWallgren commented on GitHub (Jun 17, 2023):

It should be sufficient with "only" 6 GB of memory after applying the following patch, https://github.com/hoppscotch/hoppscotch/pull/3148.

@NicklasWallgren commented on GitHub (Jun 17, 2023): It should be sufficient with "only" 6 GB of memory after applying the following patch, https://github.com/hoppscotch/hoppscotch/pull/3148.

kerem referenced this issue

2026-03-17 00:38:25 +03:00

[PR #976] [MERGED] ⬆️ Bump graphql from 15.2.0 to 15.3.0 #2981