Add podman userns option and id mappings #649
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Darrenn Jackson <darrenn.jackson@hpe.com>
Signed-off-by: Darrenn Jackson <darrenn.jackson@hpe.com>
Signed-off-by: Roger Sheen <roger@infotexture.net>
infotexture
approved these changes
Dec 7, 2025
Member
infotexture
left a comment
infotexture
left a comment
There was a problem hiding this comment.
@darrenn-jackson Thanks, looks good, merging…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add the necessary
--usernsoption string to instructions for using Podman to build via the toolkit container image. Switch the Note type to "Important" because without adding this option, building using Podman fails.Motivation and Context
This fixes Issue #639. See that issue for full details and rationale for this change.
How Has This Been Tested?
I tested the full
podmancommand given here (within Ubuntu WSL2 and in our Jenkins CI/CD environment) as part of my org's migration from Docker to Podman in our CI/CD environment several months ago. We run the DITA-OT 4.2.3 container image (with some custom plugins installed) in production for our docs builds for every docs PR and active branch within several repos. I also verified this Podman command & option with the DITA-OT 4.3 container image.Type of Changes
Documentation and Compatibility
No further change needed to the docs. No changes need for user plug-ins. All docs changes are in this PR.
I wrote the change in this PR in a version-agnostic way so that we just can cherry-pick this it to the other docs release branches. This does not break backwards compatibility or other users' overrides.
Checklist
The following checklist items are not applicable because this is a docs-only change that doesn't change the DITA-OT toolkit itself, only the instructions for one of the container engines used to run it: