docs: document dev container runtime limitations - #1900
Conversation
The dev container builds this repository only, so ll-box (from the separate linyaps-box project) and the installed config.yaml under $LINGLONG_DATA_DIR are missing, and sandbox or repository commands fail with errors that do not point at the cause. Document both workarounds and mention ll-cli doctor, which reports each component with a hint.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: unbridled-41 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @unbridled-41. Thanks for your PR. I'm waiting for a OpenAtom-Linyaps member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
2 participants
Summary
Document why sandbox and repository commands fail out of the box in the dev container and their workarounds.
Root cause
The container builds this repository only: the default OCI runtime
ll-boxcomes from the separate linyaps-box project, andconfig.yamlunderLINGLONG_DATA_DIRis only installed bymake install. Both gaps surface as unrelated-looking errors (ll-box not found,all failedfrom repository config loading).Changes
DEVELOPMENT_CONTAINER.mdwith the two workarounds (LINGLONG_OCI_RUNTIMEoverride, copyingmisc/share/linglong/config.yaml) and a pointer toll-cli doctor.Test plan