Cannot start wasabi container on Ubuntu 16.04

[mhyndle]

I wanted to give Wasabi a try and install it locally. As I'm working on Windows at the moment, I have set up virtual machine with Vagrant with clean Ubuntu 16.04. I did steps from README to install Wasabi on Ubuntu, but it is failing on creating wasabi container. Bootstrap and build processes finished without errors. Cassandra and MySQL containers are running, but when trying to run ./bin/wasabi.sh start:wasabi it fails with following message:

wasabi: building
Sending build context to Docker daemon  49.64MB
Step 1/22 : FROM centos
 ---> 49f7960eb7e4
Step 2/22 : ENV WASABI_MODULE wasabi-main
 ---> Using cache
 ---> cbf7e76b6f6f
Step 3/22 : ENV WASABI_UI_MODULE wasabi-ui-main
 ---> Using cache
 ---> 232bc3be7de1
Step 4/22 : ENV WASABI_PORT 8080
 ---> Using cache
 ---> 8191c0f47565
Step 5/22 : ENV WASABI_JMX_PORT 8090
 ---> Using cache
 ---> b8d6999c9d2f
Step 6/22 : ENV WASABI_DEBUG_PORT 8180
 ---> Using cache
 ---> 0d24cdb1dc37
Step 7/22 : ENV WASABI_SRC_DIR wasabi-main-1.0.20180628071500-SNAPSHOT-development
 ---> Using cache
 ---> 5ca2191d58be
Step 8/22 : ENV WASABI_HOME /usr/local/wasabi-main-1.0.20180628071500-SNAPSHOT-development
 ---> Using cache
 ---> e4076fa91beb
Step 9/22 : ENV WASABI_JAVA_OPTIONS ""
 ---> Using cache
 ---> cbf0bdb909fa
Step 10/22 : ENV JDK_MAJOR_VERSION 8u131
 ---> Using cache
 ---> f4809c4a5942
Step 11/22 : ENV JDK_MINOR_VERSION b11
 ---> Using cache
 ---> 38c776137069
Step 12/22 : ENV JDK_VERSION ${JDK_MAJOR_VERSION}-${JDK_MINOR_VERSION}
 ---> Using cache
 ---> 8c8f2d39d67d
Step 13/22 : RUN yum -y update && yum install -y wget
 ---> Running in 252196a04d10
Loaded plugins: fastestmirror, ovl
Determining fastest mirrors


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=container error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"
The command '/bin/sh -c yum -y update && yum install -y wget' returned a non-zero code: 1
wasabi: starting
Unable to find image 'wasabi-main:latest' locally
docker: Error response from daemon: repository wasabi-main not found: does not exist or no pull access.
See 'docker run --help'.
error: docker run --net=wasabi_nw --name wasabi-main -p 8080:8080 -p 8090:8090 -p 8180:8180 -e "WASABI_CONFIGURATION=-DnodeHosts=172.18.0.2 -Ddatabase.url.host=172.18.0.3" -d wasabi-main

usage: container.sh [options] [commands]

options:
  -v | --verify [ true | false ]         : verify installation configuration; default: false
  -m | --migration [ true | false ]      : refresh cassandra migration scripts; default: false
  -s | --sleep [ sleep-time ]            : sleep/wait time in seconds; default: 3
  -h | --help                            : help message

commands:
  start[:wasabi,cassandra,mysql,docker]  : start all, wasabi, cassandra, mysql, docker
  stop[:wasabi,cassandra,mysql,docker]   : stop all, wasabi, cassandra, mysql, docker
  console[:cassandra,mysql]              : console all, cassandra, mysql
  status                                 : status
  remove[:wasabi,cassandra,mysql]]       : remove all, wasabi, cassandra, mysql

From what I checked, it seems that mirrorlist URL for yum is incorrect.
Is there any way to fix that?

[vnaidu-wish]

facing the same error.

[rharriso]

I was able to work around this. I found out that my company has internal centos mirrors.

RUN cat /etc/resolv.conf
# private corporate mirrors

So I disconnected from the corporate vpn, then was able to start up the image.

[fanker]

facing the same error. Is there anyone can fix it ?

[fanker]

facing the same error. Is there anyone can fix it ?
I have resolve it by update nameserver to 8.8.8.8 / 8.8.4.4 / 114.114.114.114.
And how to update nameserver in ubuntu ?

1. vim /etc/resolvconf/resolv.conf.d/base
   insert
   nameserver 8.8.8.8
   or
   nameserver 114.114.114.114 (if your server in china)
   to the first line
   then exec :wq save it
2. exec /etc/init.d/networking restart
3. cat /etc/resolv.conf, you will find the new nameserver config
4. reexec ./bin/wasabi.sh build start
5. Congratulations! It worked.