Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
#991 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@kay-schecker ya está trabajando en esto.

Desde el 9/9/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
2k
Forks
208
Merge medio
7 h 12 min
PR fusionados (30 d)
6

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenAPITools/openapi-generator-cli

Todos los issues de OpenAPITools/openapi-generator-cli

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.