Sorry - I didn't answer one of your questions. Yes, I am able to build metron-config and full-dev is working fine for me from master.
Jon On Wed, Nov 22, 2017 at 7:11 AM [email protected] <[email protected]> wrote: > It looks like you have two issues - one related to having java_home unset, > and one with an old version of npm. > > I would suggest focusing on the Vagrant spin-up, as it is the easiest to > get running. Are you running this on a CentOS 6 machine, or are you > referring to the full-dev VM's CentOS 6 OS? Also, you have noted that this > affects version 0.4.0, but the latest release is 0.4.1, is that accurate? > Have you retried the `vagrant up` after your npm upgrade and a npm` cache > clean`? > > Jon > > On Wed, Nov 22, 2017 at 7:01 AM Pawel Bialasiewicz <[email protected]> > wrote: > >> Hi, >> >> >> I have been trying to run Metron in many ways and all of the deployment >> methods failed: >> >> >> 1) Bare metal –-> [Issue 1320] >> >> 2) AWS –-> [Issue 1318] >> >> 3) Vagrant –-> [Issue 1327] >> >> >> So currently I'm out of options. All the deployments methods failed. >> >> >> Is the all of documentation outdated, or maybe I should use a more >> specific branch(other then master)? >> >> >> Can somebody confirm that it is currently possible to build >> metron-config? It fails for me in every deployment. >> >> >> Any help would be appreciated. >> > -- > > Jon > -- Jon
