mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4730] [bug]: ERROR: failed to solve: process "/bin/sh -c pnpm install -f --offline" did not complete successfully: exit code: 1 #1767
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#1767
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 @Leon-Luu on GitHub (Feb 6, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4730
Is there an existing issue for this?
Current behavior
On Selfhost version 2025.1.0 when peform build it failed:
"ERROR: failed to solve: process "/bin/sh -c pnpm install -f --offline" did not complete successfully: exit code: 1"
Full error log below:
I tried to change the RUN pnpm install -f --offline to only RUN pnpm install -f in prod.Dockerfile and it will failed on later phase with bcrypt:
Steps to reproduce
docker build -t my_hoppscotch_backend:latest -f ./prod.Dockerfile --target backend .
Environment
Production
Version
Self-hosted
@blfrie commented on GitHub (Feb 6, 2025):
I would like to add that this happens with the docker compose approach also, which is expected since it uses the same prod.Dockerfile. But wanted to add the info just in case.
Steps to reproduce
mv .env.example .envdocker compose up -d hoppscotch-aio@liyasthomas commented on GitHub (Feb 6, 2025):
We’ve identified a fix for this behavior that occurs during build time. It’s due to an issue with pnpm version 10. Reference. To mitigate this issue until the core team implements future fixes, it’s recommended to temporarily downgrade pnpm to version 9.
We’ve also opened a PR that will pin the pnpm version to v9, which will temporarily resolve this issue. The fix is scheduled for the next immediate point release, so please be patient while we conduct our internal audits and reviews for the release.
@liyasthomas commented on GitHub (Feb 7, 2025):
Thanks for your patience and valuable feedback. This issue has been resolved in the latest release.
Closing this ticket as the fix is now available in the recent version. Please feel free to reach out if you have any other concerns.