These are chat archives for nlf/dlite

Nov 2016
Joel Baranick
Nov 06 2016 17:55
Something happened with dlite and now I can not longer start the VM.
When I run dlite start it exits after 30s with
Starting the virtual machine: ERROR!
Timed out waiting for virtual machine
So I tried stopping the dlite daemon and running it manually via: sudo dlite daemon.
Not when I run dlite start it still times out after 30s, but from sudo dlite daemon I get 110616.095503 POST /start [500] 30096908ms
Joel Baranick
Nov 06 2016 18:01
Even after dlite start times out, dlite status returns that it is running fine:
vm_state:       started
pid:            6432
id:             7293d58d-9f7a-11e6-9f4f-24a074f03d14
hostname:       local.docker
disk_size:      20
disk_path:      /Users/my_user/.dlite/disk.qcow
cpu_cores:      4
memory:         6
docker_version: latest
However, docker version reports:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 23:26:11 2016
 OS/Arch:      darwin/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
Joel Baranick
Nov 06 2016 18:06
The docker.sock file exists:
~ ❯❯❯ ls -al /var/run/docker.sock                                      ⮂ LOCAL
srwxrwxrwx  1 root  daemon  0 Nov  6 10:03 /var/run/docker.sock
The /etc/resolver/docker file exists:
~ ❯❯❯ cat /etc/resolver/docker                                         ⮂ LOCAL
port 1053
The /etc/exports file exists:
~ ❯❯❯ cat /etc/exports                                                 ⮂ LOCAL

/Users/my_user -network -mask -alldirs -maproot=root:wheel
Joel Baranick
Nov 06 2016 18:18
Who knows what happened, but after I stopped dlite daemon, deleted /Users/my_user/.dlite, ran dlite init, restarted dlite daemon, and ran dlite start everything works.
@nlf I know you are working on it, but logging would go a long way to making this type of issue both easier to resolve and to diagnose.