Uploaded image for project: 'MusicBrainz Virtual Machines'
  1. MusicBrainz Virtual Machines
  2. MBVM-19

Docker / Vagrant VM is not accessible (neither localhost:5000, nor 127.0.0.1:5000) / Steps to make it working in VMWare Workstation

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Normal Normal
    • None
    • None

      I'm not sure if this is the right place for issues with the Docker/Vagrant VM

      I followed the installation steps from https://github.com/metabrainz/musicbrainz-vm
      including the bin/reindex

      Today I have updated the Vagrant box with
      sudo vagrant box update
      (to 20160815.0.0 because my 20160809.1.0 was no more the most actual version)

      Both version are not accessible from localhost:5000 or 127.0.0.1:5000 in my VMWare Workstation Ubuntu Environment.

      If I connect to vagrant with
      cd musicbrainz-vm
      sudo vagrant ssh

      and then execute the commands
      sudo docker-compose stop musicbrainz
      then
      sudo docker-compose build musicbrainz
      then
      sudo docker-compose up (without '-d --no-deps musicbrainz' which doesn't work, only gives the ERROR
      ERROR: Cannot link to a non running container: /musicbrainzdocker_search_1 AS /musicbrainzdocker_musicbrainz_1/musicbrainzdocker_search_1)

      I get many warnings. You will find the logfile attached.

      The good thing:
      After manually executing the above steps, I can access the GUI with 127.0.0.1:5000 and localhost:5000
      I can use this Docker / Vagrant VM including the Search Server completely offline!

      Maybe you can have a look at the attached logfile and fix all the

      Argument "Moose::Meta::Method=HASH(0x349a570)" isn't numeric in numeric eq (==) at /usr/local/share/perl/5.22.1/MooseX/ABC/Trait/Class.pm line 61

      and all the supposed missing indexes, like

      search_1 | WARNING: Could not load recording index: directory '/home/search/data/recording_index' does not exist

      It would be great, if the last manual step ("sudo docker-compose up") would be executed automatically with the "sudo vagrant up" command.

            rob Robert Kaye
            invisibleman78 Invisible Man
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package