joufellasfl
commented
6 months ago Thanks for the report @miellaby, a change was added to handle this case in the master branch, would you be able to test it in your environment ?
Open miellaby opened 7 months ago
joufellasfl
commented
6 months ago Thanks for the report @miellaby, a change was added to handle this case in the master branch, would you be able to test it in your environment ?
Context: Using cqfd from a host user (jenkins) who has no user group. For example, on our server, jenkins belongs to the docker group only (which is its primary group).
Expected: commands run by cqfd inherits the credentials/ownership of the host user. Especially files generated by cqfd encapsulated commands have the same user and group than the files generated without cqfd. In our case, generated files should be owned by jenkins:docker (user jenkings group docker).
Observed: files generated within cqfd are owned by jenkins:jenkins instead of jenkins:docker
Correction proposal (TBC): In make_launch() bash function, useradd should be called with the --no-user-group option to make the docker user consistent with the host user (that is with the same primary group).