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

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

Github user jameslamb commented on the issue:

    https://github.com/apache/metron/pull/1091
  
    I THINK I found the issue with my original PR. The command to register the 
scl repo doesn't get picked up by `yum` until it exits.
    
    **this fails to find devtoolset-4**
    
    ```
    yum install -y \
        centos-release-scl \
        devtoolset-4-gcc-c++
    ```
    
    **this finds it**
    
    ```
    yum install -y centos-release-scl \
    && yum install -y devtoolset-4-gcc-c++
    ```
    
    Testing locally now, will update later tonight. I am testing locally by 
walking through the build instructions in each README in the 
`metron-deployment/packaging/docker` sub-folders. I've never used vagrant and 
don't actually know how to do "Have you verified the basic functionality of the 
build by building and running locally with Vagrant full-dev environment or the 
equivalent?"


> Packaging docker containers are too large
> -----------------------------------------
>
>                 Key: METRON-1650
>                 URL: https://issues.apache.org/jira/browse/METRON-1650
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: James Lamb
>            Priority: Minor
>
> I have been looking through the project source code, and found that the 
> packaging docker containers are bigger than they need to be. 
> The containers' size could be cut substantially by:
>  * Grouping as many commands as possible into as few RUN stages as possible
>  * Taking advantage of `yum clean` and `apt-get clean`
>  * Removing artifacts pulled with `wget`
>  * Removing unused libraries or libraries only needed at build time (like 
> `tar` and `wget`)
> I am creating this issue but will soon submit a PR to address it.
> Thank you for considering my proposal!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to