-
-
Notifications
You must be signed in to change notification settings - Fork 292
fix(docker): Resolve build failure and clarify documentation #1783
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
base: main
Are you sure you want to change the base?
fix(docker): Resolve build failure and clarify documentation #1783
Conversation
…ck to use the correct Yarn version and copying the yarn.lock file to satisfy the --immutable install flag. Fixes json-schema-org#1782
…-org#1782 Revised the Docker section to provide clearer, step-by-step instructions for building and running the development environment using Docker. Added details about directory navigation, image naming, port mapping, and live code updates.
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to the JSON Schema Community. Thanks a lot for creating your first pull request!! 🎉🎉 We are so excited you are here! We hope this is only the first of many! For more details check out README.md file.
This comment was marked as outdated.
This comment was marked as outdated.
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1783 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 31 31
Lines 636 636
Branches 196 196
=========================================
Hits 636 636 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This comment was marked as outdated.
This comment was marked as outdated.
3 similar comments
Hi @elyashium! Thanks a lot for your contribution! I noticed that the following required information is missing or incomplete: kind of change description Please update the PR description to include this information. You can find placeholders in the PR template for these items. Thanks a lot! |
Hi @elyashium! Thanks a lot for your contribution! I noticed that the following required information is missing or incomplete: kind of change description Please update the PR description to include this information. You can find placeholders in the PR template for these items. Thanks a lot! |
Hi @elyashium! Thanks a lot for your contribution! I noticed that the following required information is missing or incomplete: kind of change description Please update the PR description to include this information. You can find placeholders in the PR template for these items. Thanks a lot! |
What kind of change does this PR introduce?
A bugfix for the Docker build process and a documentation update.
Issue Number:
Screenshots/videos:
If relevant, did you update the documentation?
Yes, the
INSTALLATION.md
file has been updated to provide clearer and more accurateinstructions for running the project with Docker.
Summary
This pull request resolves a critical failure in the Docker build process. The build was
failing for two reasons:
Dockerfile
did not enablecorepack
, leading to a Yarn version mismatch as specifiedin
package.json
.Dockerfile
did not copy theyarn.lock
file, causing theyarn install --immutable
command to fail as it requires the lockfile to be present.
This PR corrects the
Dockerfile
by adding the necessarycorepack enable
command andincluding
yarn.lock
in the files copied to the image.Additionally, the "Run locally using Docker" section of
INSTALLATION.md
has beenrewritten to be more explicit, removing the reliance on
make
and providing direct,cross-platform
docker
commands to improve clarity and accessibility for all developers.Does this PR introduce a breaking change?
No, this PR fixes a broken process and makes it work as intended.
Checklist
Please ensure the following tasks are completed before submitting this pull request.