[
https://issues.apache.org/jira/browse/METRON-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803295#comment-15803295
]
ASF GitHub Bot commented on METRON-644:
---------------------------------------
Github user kylerichardson commented on the issue:
https://github.com/apache/incubator-metron/pull/409
@justinleet Good catch. Updated the README to remove the note about Docker
for Mac.
> RPM builds only work with Docker for Mac
> ----------------------------------------
>
> Key: METRON-644
> URL: https://issues.apache.org/jira/browse/METRON-644
> Project: Metron
> Issue Type: Bug
> Reporter: Kyle Richardson
> Assignee: Kyle Richardson
> Priority: Minor
>
> Currently using the rpm-docker container for building Metron RPMs will only
> work on Docker for Mac due to permissions issues on the SOURCE/* and SPEC/*
> files.
> When using docker-machine (e.g. boot2docker) or a local docker install on
> Linux, the build fails due to "Bad owner/group." After some research, this
> apparently occurs due to the uid/gid of the files not being a valid user
> and/or group in the container OS.
> I'd like to avoid changing permissions on these files to root, so that the
> developer can maintain non-root ownership of the files in his/her development
> environment. To do that, I propose adding a few checks to the build.sh script
> to:
> # check if the owner of the SPEC/metron.spec file exists in the container OS
> # if not, create that user
> # once the build is complete, change ownership of the build files (e.g. RPMs)
> to the original owner
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
