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
Add a configuration to jib-maven-plugin/jib-gradle-plugin that can define the userid/groupid to set for the files we build into the container, similar to how Dockerfile's COPY --chown works. The container configuration User field should also be set accordingly.
chown can either be a single uid or a string of the form uid:gid.
So, for example, in your case, the configuration could look something like:
Just FTR: files are already readable and possibly executable for any, so it doesn't seem necessary to set user and group IDs. At least we don't see a use case for it for now.
NOT READY
Regards #727
Add a configuration to
jib-maven-plugin
/jib-gradle-plugin
that can define the userid/groupid to set for the files we build into the container, similar to how Dockerfile'sCOPY --chown
works. The container configurationUser
field should also be set accordingly.chown
can either be a single uid or a string of the formuid:gid
.So, for example, in your case, the configuration could look something like:
Maven:
Gradle:
Tasks:
OwnerGroup
to represent a pair of user id and group id (group id defaults to user id if not given).User
field toContainerConfigurationTemplate
.OwnerGroup
toBuildConfiguration
.OwnerGroup
to build the layer files.jib-maven-plugin
chown
parameter.jib-gradle-plugin
chown
parameter.The text was updated successfully, but these errors were encountered: