I did a ‘reinstall’ and some restarting. I have a feeling that the way that MS instantiates the VM with Docker included as an ‘extension’ is part of the problem. I show input from docker info and which below.
bdelaney@dfdiscourse:~$ docker version
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
FATA Get http:///var/run/docker.sock/v1.16/version: dial unix /var/run/doc
ker.sock: no such file or directory. Are you trying to connect to a TLS-enabled
daemon without TLS?
bdelaney@dfdiscourse:~$ which docker.io
bdelaney@dfdiscourse:~$ which docker
The command docker info does not work at all. I get the following:
bdelaney@dfdiscourse:~$ docker info
FATA Get http:///var/run/docker.sock/v1.16/info: dial unix /var/run/docker
.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?
In another local VM (not MS installed on Azure) I’m running docker and both docker info and docker version work. But in that VM Docker is not installed in /usr/local/bin. In the Azure VM I’m trying to install Discourse to, docker.sock does not appear to exist under /var/run. Thus the output above for info and version.
My reinstall and restart did not seem to accomplish anything.
Not a Linux user so this is a little foreign to me. But I followed the ‘prescribed’ way to bring up a docker enabled VM in Azure. I did this with Azure xplat-cli tools running in a local Ubuntu VM
From reading the Launcher script I doubt that I can just use the Docker tools to bring up a container myself without using your bootstrap process. But at this point, I think the problem lies with the special MS install pattern. I believe that this is a possible use case for you in the future though as many developers will operate a Linux VM in the MS Azure cloud. And they are being ‘proscriptive’ about how to create Dockerized Linux VMs.
Happy to provide more details and take steps to reproduce the problem. Will follow any recommendations you make and I’ll keep on troubleshooting via Google as much as possible.
I think the ideas behind Discourse and its implementation are great. I had a taste of it with my blog when I brought up the Bitnami instance, but then decided to follow your latest recommendation regarding Docker. I’m willing to go the extra mile to get it working on Azure and I’ll document it comprehensively if I ever get it running.