redhat-developer / redhat-developer/abbenay
docs(container): document concrete path to gRPC ca.crt inside the image
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 7
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 3
Description
Context
With the container default CMD using --grpc-tls, clients must trust the daemon CA. Docs refer to <runtime-dir>/tls/ca.crt but do not give the concrete in-container path (typically under /tmp/abbenay/tls/ when XDG_RUNTIME_DIR is unset) or a podman cp / volume-mount example.
Flagged during review of PR #63: https://github.com/redhat-developer/abbenay/pull/63
Proposal
- Add an explicit example path for the UBI image user
- Show
podman cp <ctr>:/tmp/abbenay/tls/ca.crt ./ca.crt(or whatever path is correct after verifying) - Cross-link from Python README container section
References
- PR #63
- docs/CONTAINER.md
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/CONTAINER.md and the Python README container section. Verify the concrete CA path when XDG_RUNTIME_DIR is unset, then document the podman cp or volume-mount example and add the cross-link. Done means the UBI image path and a usable client-trust workflow are explicit in both documentation locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 76/100