You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
miellaby
changed the title
Issue if user has no user-group
Files ownership issue if host user has no user group
Feb 6, 2024
miellaby
changed the title
Files ownership issue if host user has no user group
Files ownership issue when host user has no user group
Feb 6, 2024
This issue was reported in #123, where @miellaby wrote:
> 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 (-N) option to make the
> docker user consistent with the host user (that is with the same
> primary group).
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).
The text was updated successfully, but these errors were encountered: