[ 
https://issues.apache.org/jira/browse/METRON-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267623#comment-16267623
 ] 

ASF GitHub Bot commented on METRON-1333:
----------------------------------------

Github user ottobackwards commented on a diff in the pull request:

    https://github.com/apache/metron/pull/848#discussion_r153332780
  
    --- Diff: metron-deployment/packaging/docker/ansible-docker/Dockerfile ---
    @@ -14,13 +14,18 @@
     #  See the License for the specific language governing permissions and
     #  limitations under the License.
     #
    -FROM centos:centos6
    +FROM centos:centos6.9
     MAINTAINER Apache Metron
     
     RUN yum install -y tar
     RUN yum install -y wget
    +# base development tools required
     RUN yum groupinstall -y "Development tools"
    +# newer cpp 11 support required for building node modules
    +RUN wget http://people.centos.org/tru/devtools-2/devtools-2.repo -O 
/etc/yum.repos.d/devtools-2.repo
    --- End diff --
    
    yeah, thanks.  Nick also pointed this out in a jira ( referring to your 
steps ), i'll have this in in a moment


> Ansible-Docker can no longer build metron
> -----------------------------------------
>
>                 Key: METRON-1333
>                 URL: https://issues.apache.org/jira/browse/METRON-1333
>             Project: Metron
>          Issue Type: Bug
>    Affects Versions: 0.4.2
>            Reporter: Otto Fowler
>            Assignee: Otto Fowler
>            Priority: Critical
>
> The ansible-docker container could be used to build metron ( even the rpms ) 
> and run the ansible scripts.  This is no longer true, as the new node ui 
> projects have native compilation that requires c++ 11 support in gcc, and rpm 
> build requires node to be installed ( not local installed as in the mvn 
> packaging ).
> Many users are having problems building metron on centos platforms, having 
> this container available and functioning would be a great help



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to