404 while trying to reach http://docker-registry.vagrant.f8

[Austin Lowry]

I have a new install of fabric8 running on the Vagrant image. My machine is OS X, 10.4.4.

I had some issues getting going where the networking would error out, but this fix to Vagrant moved me past that.

Now most everything appears to be working, but I'm getting a 404 for http://docker-registry.vagrant.f8. Being new to the platform, I'm at a bit of a loss where to start troubleshooting. 

If I run vagrant version from the command line of my OS X system I get the following:

>docker version

Client version: 1.6.2

Client API version: 1.18

Go version (client): go1.4.2

Git commit (client): 7c8fca2

OS/Arch (client): darwin/amd64

FATA[0000] Get http://vagrant.f8:2375/v1.18/version: dial tcp: lookup vagrant.f8: no such host. Are you trying to connect to a TLS-enabled daemon without TLS? 

That URL does resolve in the browser (and command line) and returns:

{"ApiVersion":"1.18","Arch":"amd64","GitCommit":"c3ca5bb/1.6.2","GoVersion":"go1.4.2","KernelVersion":"3.10.0-229.7.2.el7.x86_64","Os":"linux","Version":"1.6.2.el7"} 

The VBox host returns the following:

> docker version

Client version: 1.6.2.el7

Client API version: 1.18

Go version (client): go1.4.2

Git commit (client): c3ca5bb/1.6.2

OS/Arch (client): linux/amd64

Server version: 1.6.2.el7

Server API version: 1.18

Go version (server): go1.4.2

Git commit (server): c3ca5bb/1.6.2

OS/Arch (server): linux/amd64 

One more clue, which may be unrelated. The openshift logs have a lot of this:

E0719 13:00:19.349768    4462 reflector.go:133] Failed to list *api.Namespace: Get https://172.28.128.4:8443/api/v1/namespace

If I go to that URL, the JSON returned is:

{

  "kind": "Status",

  "apiVersion": "v1",

  "metadata": {},

  "status": "Failure",

  "message": "User \"system:anonymous\" cannot list all namespace in the cluster",

  "reason": "Forbidden",

  "details": {},

  "code": 403

}

All this seems to add up to something not quite configured correctly, but I'm not sure where or what to do to troubleshoot next. Thanks for the help.