Kolla vagrant docker typo

Bug #1542916 reported by serlex on 2016-02-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Low
Steven Dake

Bug Description

I'm trying to test kolla using the Vagrant documentation. However docker in Operator box didn't start properly:

==> operator: setenforce: SELinux is disabled
==> operator: Get http:///var/run/docker.sock/v1.20/containers/json?all=1&filters=%7B%22name%22%3A%5B%22registry%22%5D%7D: dial unix /var/run/docker.sock: no such file or directory.
==> operator: * Are you trying to connect to a TLS-enabled daemon without TLS?
==> operator: * Is your docker daemon up and running?
==> operator: Post http:///var/run/docker.sock/v1.20/containers/create?name=registry: dial unix /var/run/docker.sock: no such file or directory.
==> operator: * Are you trying to connect to a TLS-enabled daemon without TLS?

[root@operator vagrant]# systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: error (Reason: Bad message)
   Active: inactive (dead)\
     Docs: http://docs.docker.com

Feb 07 19:13:21 operator.local systemd[1]: [/usr/lib/systemd/system/docker.service:14] Missing '='.

ExecStart=/usr/bin/docker -d --insecure-registry operator.local:4000 --registry-mirror=http://operator.local:4000

From what I understand the above is missing a '\' after 4000

Cheers

Steven Dake (sdake) on 2016-02-18
Changed in kolla:
status: New → Triaged
importance: Undecided → Low
milestone: none → mitaka-3
Martin André (mandre) wrote :

I can't reproduce the issue in my environment.

Did you run "vagrant up" from a fresh Kolla checkout? Do you have a Vagrantfile.custom file?

serlex (serlex) wrote :

Closing as I'm unable to reproduce any more

Changed in kolla:
status: Triaged → Invalid
Steven Dake (sdake) on 2016-03-05
Changed in kolla:
assignee: nobody → Steven Dake (sdake)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers