-
Notifications
You must be signed in to change notification settings - Fork 83
docs(clp-package): Document default container configurations in the package Docker image. #1530
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?
Conversation
…ackage Docker image.
WalkthroughAdded a "Default Configurations" subsection to the clp-package tooling-containers documentation, introducing a table that documents environment variable defaults (PATH, CLP_HOME, LD_LIBRARY_PATH, PYTHONPATH, SHELL, USER) and their purposes for debugging container builds. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: ASSERTIVE Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used🧠 Learnings (7)📓 Common learnings📚 Learning: 2025-10-13T03:32:19.293ZApplied to files:
📚 Learning: 2025-09-25T05:13:13.298ZApplied to files:
📚 Learning: 2025-10-20T21:05:30.417ZApplied to files:
📚 Learning: 2025-10-07T07:54:32.427ZApplied to files:
📚 Learning: 2025-06-18T20:48:48.990ZApplied to files:
📚 Learning: 2025-08-25T16:27:50.549ZApplied to files:
🔇 Additional comments (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
| While not intended for direct end-user deployment, the container includes these configurations for | ||
| debugging purposes: |
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.
I don't think these configurations are really for debugging.
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.
Technically we don't have to create users in the image and any env var overrides can be specified only in the docker compose yamls. That said, practically we can clean up the duplicated specifications from the docker compose files now they are specified in the image
If we don't clean up, until we make the Package docker image standalone runnable, the non root user and the env vars are to help debugging the Package runtime environment
Co-authored-by: Bingran Hu <[email protected]>
| While not intended for direct end-user deployment, the container includes these configurations for | ||
| debugging purposes: | ||
|
|
||
| | Setting | Related Env Var | Value | Purpose | |
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.
I think some of these deserve more explanation. I'll come back to this PR after the release.
Description
Adds a configuration reference table to the
clp-packageDocker image documentation, documenting the default user, paths, and environment variables. This helps developers understand the container's runtime environment when debugging or extending the image.Checklist
breaking change.
Validation performed
Summary by CodeRabbit