-
Notifications
You must be signed in to change notification settings - Fork 452
docs: add Podman machine reboot step to cert install #13498
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
docs: add Podman machine reboot step to cert install #13498
Conversation
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.
Hey @alilleybrinker - I've reviewed your changes and they look great!
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
thanks @alilleybrinker for the contribution |
📝 WalkthroughWalkthroughThe documentation for adding certificates to a Podman machine was updated to include an optional step. After exiting the Podman machine, users are now advised that they may optionally reboot the machine by stopping and starting it with the commands Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 markdownlint-cli2 (0.17.2)website/docs/podman/adding-certificates-to-a-podman-machine.mdmarkdownlint-cli2 v0.17.2 (markdownlint v0.37.4) ... [truncated 1177 characters] ... 4:11) Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 1
🧹 Nitpick comments (1)
website/docs/podman/adding-certificates-to-a-podman-machine.md (1)
74-75
: Add<machine_name>
placeholder for consistency with earlier commandsAll previous machine-scoped commands include the
<machine_name>
parameter. Re-introducing it here avoids confusion for users who run multiple machines.-$ podman machine stop -$ podman machine start +$ podman machine stop <machine_name> +$ podman machine start <machine_name>
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
website/docs/podman/adding-certificates-to-a-podman-machine.md
(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: benoitf
PR: podman-desktop/podman-desktop#13043
File: packages/main/src/plugin/image-checker.ts:39-46
Timestamp: 2025-07-02T08:30:22.649Z
Learning: In Podman Desktop, benoitf prefers to add dependency injection annotations (@injectable, @inject) in separate PRs before implementing the actual container bindings and DI activation. This allows for incremental adoption of dependency injection.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)
- GitHub Check: smoke e2e tests (production)
- GitHub Check: smoke e2e tests (development)
- GitHub Check: unit tests / windows-2025
- GitHub Check: unit tests / macos-15
- GitHub Check: unit tests / ubuntu-24.04
- GitHub Check: linter, formatters
- GitHub Check: Windows
- GitHub Check: macOS
- GitHub Check: Linux
- GitHub Check: take screenshots
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This adds an optional step to the end of the instructions for installing additional root certificates to a Podman machine. On MacOS, with the podman machine default as my container host, "podman compose up" would continue to fail with self-signed certificate errors after following the instructions in this guide, until I fully rebooted the Podman machine. Signed-off-by: Andrew Lilley Brinker <alilleybrinker@gmail.com>
9a40e22
to
eae2734
Compare
Added the |
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.
Thanks, @alilleybrinker
2dcf92c
into
podman-desktop:main
What does this PR do?
This adds an optional step to the end of the instructions for installing additional root certificates to a Podman machine. On MacOS, with the podman machine default as my container host, "podman compose up" would continue to fail with self-signed certificate errors after following the instructions in this guide, until I fully rebooted the Podman machine.
What issues does this PR fix or reference?
I did not open an Issue prior to opening the PR.