OpenAPITools / OpenAPITools/openapi-generator-cli

[BUG] Unable to access files when useDocker is true and SELinux is enabled

Open
#991 0 comments 0 reactions 1 assignee View on GitHub

@kay-schecker is already working on this.

Since Sep 9, 2025.

bug
Dominant language
TypeScript
Stars
2k
Forks
208
Avg merge
7h 12m
Merged PRs (30d)
6

Description

🐛 Bug Report:

Describe the bug

The OCI container running the generator is unable to access the input files and output directory when they are in a home directory. The volume parameters are missing the :Z at the end of the parameter to enable access when SELinux is enabled. The build fails because the docker container cannot find the spec file, even though it is properly configured.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Enable SELinux on your linux workstation
  2. Check out your project into your home directory.
  3. Don't override default SELinux tags on your work directory. Leave them marked as unconfined_u:object_r:user_home_t, or however they are marked by default in your home directory. (Hint: use ls -lZ to see the SELinux markings) The markings should NOT mention container`. This would imply that the whole directory was changed to use container-friendly marking.
  4. Attempt to generate code from an api json file.
  5. See error. The build should complain that the spec file was not found.
Expected behavior

Code should be generated successfully.

Operation System (please complete the following information):
  • OS: RHEL 9
  • Version 9.6
Package System (please complete the following information):
  • Node v22.12.0
Additional context

The volume mount parameters should have a :Z at the end of the mapping (-v "<source file>:/local/input-spec:Z"). All volume mappings need this parameter.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.