[TASK] Warn that --output is resolved inside the container - #540
Conversation
The --output option of the render container is resolved inside the container: pointing it at a host path outside the mounted volume writes the files into the container file system, which --rm then discards - while the command still reports success. Add a note to the shared local-rendering include so every page showing the command carries the warning. Assisted-by: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
493abe7 to
aaeced6
Compare
CybotTM
changed the title
linawolf
left a comment
linawolf
left a comment
There was a problem hiding this comment.
The example command does not show the usage of the output parameter and usually it is not used by ppl just trying out the rendering. So I am wondering if this note block is really needed, expoaccialy since this include is included in so many places throughout the manual
Reviewer feedback: the rendering snippet does not use --output, and _LocalRendering.rst.txt is included in four places, so a note about it sits in front of readers who never pass the option. Move it to the Markdown-to-reST howto, the only page in this manual that passes --output, and shorten it to the point that matters: the path is resolved inside the container, so it has to stay below the mounted volume. Assisted-by: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
|
Moved in f855eb2. You are right that it does not belong there: |
2 participants
The
--outputoption of the render container is resolved inside the container: pointing it at a host path outside the mounted volume writes the files into the container file system, which--rmthen discards — while the command still reports success. This adds a note to the shared local-rendering include so every page showing the command carries the warning.