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

Aperta
#991 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@kay-schecker ci sta già lavorando.

Dal 9/9/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

bug

🐛 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.

Lingua principale
TypeScript
Stelle
2k
Fork
208
Merge medio
7h 12m
PR unite (30g)
6

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenAPITools/openapi-generator-cli

Tutte le issue di OpenAPITools/openapi-generator-cli

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.