Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 [Bug report]: ERROR: failed to solve: process "/bin/sh -c yarn install --frozen-lockfile" did not complete successfully: exit code: 1 #1486

Closed
3 of 4 tasks
priyankarpal opened this issue Apr 4, 2024 · 3 comments
Labels
💻 aspect: code Concerns the software code in the repository bug Something isn't working 🛠 goal: fix Bug fix stale

Comments

@priyankarpal
Copy link
Member

Descrcibe the bug?

when you want to build a docker image you will get that same error.

Steps to reproduce the bug?

.

Expected behavior

.

Desktop (Please provide your system information)

.

Mobile (Please provide your device information)

No response

Screenshot / Screenshare

No response

Relevant log output

Dockerfile.DEV:11
--------------------
   9 |     COPY ./package.json  /usr/src/app/
  10 |     
  11 | >>> RUN yarn install --frozen-lockfile
  12 |     
  13 |     EXPOSE 3000
--------------------
ERROR: failed to solve: process "/bin/sh -c yarn install --frozen-lockfile" did not complete successfully: exit code: 1

Record

Code of Conduct

  • I agree to follow this project's Code of Conduct
@priyankarpal priyankarpal added bug Something isn't working 🚦status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 💻 aspect: code Concerns the software code in the repository and removed 🚦status: awaiting triage Has not been triaged & therefore, not ready for work labels Apr 4, 2024
Copy link

github-actions bot commented Apr 4, 2024

To reduce notifications, issues are locked. Your issue will be unlocked when we add the label 🏁 status: ready for dev.

Copy link

github-actions bot commented Apr 4, 2024

Hey! contributor, thank you for opening an Issue 🎉.

@reactplay/maintainers will review your submission soon and give you helpful feedback. If you're interested in continuing your contributions to open source and want to be a part of a welcoming and fantastic community, we invite you to join our ReactPlay Discord Community.
Show your support by starring ⭐ this repository. Thank you and we appreciate your contribution to open source!
Stale Marking : After 30 days of inactivity this issue/PR will be marked as stale issue/PR and it will be closed and locked in 7 days if no further activity occurs.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 4, 2024
@reactplay reactplay unlocked this conversation Apr 4, 2024
Copy link

github-actions bot commented May 4, 2024

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!

@github-actions github-actions bot added the stale label May 4, 2024
@priyankarpal priyankarpal closed this as not planned Won't fix, can't repro, duplicate, stale May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository bug Something isn't working 🛠 goal: fix Bug fix stale
Projects
None yet
Development

No branches or pull requests

1 participant