mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4960] [bug]: Can't build 2025.3.0 due to ERR_PNPM_EAGAIN EAGAIN: resource temporarily unavailable #1878
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1878
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @LordSimal on GitHub (Apr 5, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4960
Is there an existing issue for this?
Current behavior
Just tried to update from 2025.2.3 to 2025.3.0 but get the following error when trying to get rebuild the containers.
Steps to reproduce
Logs and Screenshots
Environment
Production
Hoppscotch Version
Self-hosted
Interceptor
Not Applicable - Issue not related to network requests
Browsers Affected
No response
Operating System
Linux
Additional Information
No response
@LordSimal commented on GitHub (Apr 5, 2025):
It looks like the pnpm-lock.yaml contains a reference to a windows SWC package which of course won't work in linux.
But even if I just comment out the
COPY pnpm-lock.yaml .line inside theprod.Dockerfileto "freshly" isntall the packages, I get a similar error when it tries to finishpnpm iAlready tried to adjust the pnpm version to 10.7.1 but that won't work as well...
Something weird is going on here...
@LordSimal commented on GitHub (Apr 5, 2025):
I found https://github.com/activepieces/activepieces/issues/6736 which seems this is a docker related issue when running on top of ZFS (which we are)
I already updated the docker engine (and basically any other packages on our server) to the latest version and rebooted the machine, so that the latest ZSF version is running.
@LordSimal commented on GitHub (Apr 5, 2025):
Found the solution in https://github.com/pnpm/pnpm/issues/7024#issuecomment-1825412952
Seems like its a bug between pnpm, docker and ZFS (what a combo...)
I had to adjust
to
inside the
prod.Dockerfilefile. Now it works 🥳@LordSimal commented on GitHub (Jun 1, 2025):
So am i expected to always adjust my prod.dockerfile for every update?
@LordSimal commented on GitHub (Oct 31, 2025):
No idea why this doesn't work anymore, but with latest 2025.10.0 I had to comment out the
pnpm fetchcommand as well since it now complains about the sameEAGAINerror.Unfortunately, there is no
--package-import-method=hardlinkoption for that pnpm command.