Skip to content
This repository has been archived by the owner on Dec 1, 2018. It is now read-only.

vhost-proxy appears to have stopped working correctly #105

Open
TLyngeJ opened this issue Apr 23, 2016 · 16 comments
Open

vhost-proxy appears to have stopped working correctly #105

TLyngeJ opened this issue Apr 23, 2016 · 16 comments
Labels

Comments

@TLyngeJ
Copy link

TLyngeJ commented Apr 23, 2016

I just update my Ubuntu OS:

~ » lsb_release -a
Distributor ID: Ubuntu
Description:    Ubuntu 16.04 LTS
Release:    16.04
Codename:   xenial

I also update dsh:

~ » dsh version
dsh version: 1.13.0

After this, the vhost-proxy has started throwing 503 errors at me no matter what *.drude domain I try to access. I had a look in the docker logs for the container and found this:

~ » docker logs efb7f05ffa2c
/usr/lib/python2.7/site-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2016-04-23 12:41:24,740 CRIT Supervisor running as root (no user in config file)
2016-04-23 12:41:24,740 WARN Included extra file "/etc/supervisor.d/docker-gen.ini" during parsing
2016-04-23 12:41:24,748 INFO RPC interface 'supervisor' initialized
2016-04-23 12:41:24,748 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2016-04-23 12:41:24,748 INFO supervisord started with pid 1
2016-04-23 12:41:25,751 INFO spawned: 'dnsmasq' with pid 9
2016-04-23 12:41:25,753 INFO spawned: 'docker-gen' with pid 10
2016/04/23 12:41:25 error listing containers: Get http://unix.sock/containers/json: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:41:25 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016-04-23 12:41:26,764 INFO success: dnsmasq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-04-23 12:41:26,764 INFO success: docker-gen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016/04/23 12:41:35 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:41:45 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:41:55 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:42:05 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:42:15 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:42:25 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:42:35 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:42:45 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:42:55 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:43:05 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:43:15 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
192.168.10.1 [23/Apr/2016:12:43:18 +0000] "GET / HTTP/1.1" 503 614 "-"
192.168.10.1 [23/Apr/2016:12:43:19 +0000] "GET /favicon.ico HTTP/1.1" 503 614 "http://environ.drude/"
2016/04/23 12:43:25 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:43:35 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:43:45 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:43:55 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted
2016/04/23 12:44:05 Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted

I suspect that the Unable to ping docker daemon: Get http://unix.sock/_ping: dial unix /tmp/docker.sock: socket: operation not permitted has something to do with it, but I can't be sure as I do not know if that error message was there before.

These are the containers that I have running:

~ » docker ps
CONTAINER ID        IMAGE                                    COMMAND                  CREATED             STATUS              PORTS                                                  NAMES
8aee9de20663        blinkreaction/drupal-apache:2.2-stable   "/opt/startup.sh apac"   47 seconds ago      Up 47 seconds       0.0.0.0:32774->80/tcp, 0.0.0.0:32773->443/tcp          environ_web_1
d6dcf015b5f0        blinkreaction/drupal-cli:stable          "/opt/startup.sh gosu"   48 seconds ago      Up 47 seconds       9000/tcp                                               environ_cli_1
96101523a927        blinkreaction/drupal-mysql:5.5           "/entrypoint.sh mysql"   48 seconds ago      Up 47 seconds       0.0.0.0:32772->3306/tcp                                environ_db_1
e9d926da9ea0        blinkreaction/dns-discovery:stable       "/opt/entrypoint.sh s"   2 minutes ago       Up 2 minutes        192.168.10.10:53->53/udp                               dns
efb7f05ffa2c        blinkreaction/nginx-proxy:stable         "supervisord -n"         2 minutes ago       Up 2 minutes        192.168.10.10:80->80/tcp, 192.168.10.10:443->443/tcp   vhost-proxy

I believe that I am using the latest image versions:

~ » docker images
REPOSITORY                    TAG                 IMAGE ID            CREATED             SIZE
selenium/standalone-chrome    latest              17976a3a2851        4 days ago          785.1 MB
blinkreaction/drupal-apache   2.2-stable          7f72efb2c8d6        4 weeks ago         196.3 MB
blinkreaction/drupal-cli      stable              5aa76bac2c36        3 months ago        843.9 MB
blinkreaction/dns-discovery   stable              b0a0081c5c47        6 months ago        55.76 MB
blinkreaction/nginx-proxy     stable              20d0b65f6b07        6 months ago        57.56 MB
blinkreaction/drupal-mysql    5.5                 e27297c93ff0        6 months ago        235.8 MB

And if it's any use to you, this is a docker inspect on the nginx-proxy container:

~ » docker inspect efb7f05ffa2c
[
    {
        "Id": "efb7f05ffa2c367b1fd7951b3424603acfcd7b78ee4629c8460ac757813242af",
        "Created": "2016-04-23T12:41:24.061330049Z",
        "Path": "supervisord",
        "Args": [
            "-n"
        ],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 6862,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2016-04-23T12:41:24.674039937Z",
            "FinishedAt": "0001-01-01T00:00:00Z"
        },
        "Image": "sha256:20d0b65f6b078abaf5bfc419e354c57429816bf461100a73c3bbb9a9345432d9",
        "ResolvConfPath": "/var/lib/docker/containers/efb7f05ffa2c367b1fd7951b3424603acfcd7b78ee4629c8460ac757813242af/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/efb7f05ffa2c367b1fd7951b3424603acfcd7b78ee4629c8460ac757813242af/hostname",
        "HostsPath": "/var/lib/docker/containers/efb7f05ffa2c367b1fd7951b3424603acfcd7b78ee4629c8460ac757813242af/hosts",
        "LogPath": "/var/lib/docker/containers/efb7f05ffa2c367b1fd7951b3424603acfcd7b78ee4629c8460ac757813242af/efb7f05ffa2c367b1fd7951b3424603acfcd7b78ee4629c8460ac757813242af-json.log",
        "Name": "/vhost-proxy",
        "RestartCount": 0,
        "Driver": "aufs",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": [
                "/var/run/docker.sock:/tmp/docker.sock"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {}
            },
            "NetworkMode": "default",
            "PortBindings": {
                "443/tcp": [
                    {
                        "HostIp": "192.168.10.10",
                        "HostPort": "443"
                    }
                ],
                "80/tcp": [
                    {
                        "HostIp": "192.168.10.10",
                        "HostPort": "80"
                    }
                ]
            },
            "RestartPolicy": {
                "Name": "always",
                "MaximumRetryCount": 0
            },
            "AutoRemove": false,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "CapAdd": null,
            "CapDrop": null,
            "Dns": [],
            "DnsOptions": [],
            "DnsSearch": [],
            "ExtraHosts": null,
            "GroupAdd": null,
            "IpcMode": "",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "StorageOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "ConsoleSize": [
                0,
                0
            ],
            "Isolation": "",
            "CpuShares": 0,
            "Memory": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": null,
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": [],
            "DiskQuota": 0,
            "KernelMemory": 0,
            "MemoryReservation": 0,
            "MemorySwap": 0,
            "MemorySwappiness": -1,
            "OomKillDisable": false,
            "PidsLimit": 0,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "BlkioIOps": 0,
            "BlkioBps": 0,
            "SandboxSize": 0
        },
        "GraphDriver": {
            "Name": "aufs",
            "Data": null
        },
        "Mounts": [
            {
                "Source": "/var/run/docker.sock",
                "Destination": "/tmp/docker.sock",
                "Mode": "",
                "RW": true,
                "Propagation": "rprivate"
            }
        ],
        "Config": {
            "Hostname": "efb7f05ffa2c",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "443/tcp": {},
                "80/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "DOCKER_GEN_VERSION=0.4.2",
                "DOCKER_HOST=unix:///tmp/docker.sock"
            ],
            "Cmd": [
                "supervisord",
                "-n"
            ],
            "Image": "blinkreaction/nginx-proxy:stable",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": {}
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "b79a4b7f29baf382f63a889f5c723fec3a235ab978d1e6c139dfa7ea3aae3d16",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {
                "443/tcp": [
                    {
                        "HostIp": "192.168.10.10",
                        "HostPort": "443"
                    }
                ],
                "80/tcp": [
                    {
                        "HostIp": "192.168.10.10",
                        "HostPort": "80"
                    }
                ]
            },
            "SandboxKey": "/var/run/docker/netns/b79a4b7f29ba",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "37952d61554f5edabf6973e51d457c0d83c0f7fc523eec30b9b3c5aee8d77811",
            "Gateway": "172.17.0.1",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "172.17.0.4",
            "IPPrefixLen": 16,
            "IPv6Gateway": "",
            "MacAddress": "02:42:ac:11:00:04",
            "Networks": {
                "bridge": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "ca5c513fdba0dfdfdba8991645dec0d5306520bffe946d9854e3f0a6d75505e3",
                    "EndpointID": "37952d61554f5edabf6973e51d457c0d83c0f7fc523eec30b9b3c5aee8d77811",
                    "Gateway": "172.17.0.1",
                    "IPAddress": "172.17.0.4",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:ac:11:00:04"
                }
            }
        }
    }
]
@TLyngeJ TLyngeJ changed the title vhost-proxy has appears to have stopped working correctly vhost-proxy appears to have stopped working correctly Apr 23, 2016
@lmakarov
Copy link
Owner

@TLyngeJ

I've not yet tested Drude/Docker with Ubuntu 16.04.
What are your docker and docker-compose versions?

docker version
docker-compose version

Try running dsh install prerequisites - this should recreate the vhost-proxy and dns service containers on Ubuntu.

@TLyngeJ
Copy link
Author

TLyngeJ commented Apr 25, 2016

» docker version
Client:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:43:40 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.0
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   4dc5990
 Built:        Wed Apr 13 18:43:40 2016
 OS/Arch:      linux/amd64
» docker-compose version
docker-compose version: 1.5.0
docker-py version: 1.5.0
CPython version: 2.7.9
OpenSSL version: OpenSSL 1.0.1e 11 Feb 2013

@TLyngeJ
Copy link
Author

TLyngeJ commented Apr 25, 2016

I've tried to completely wipe docker and drude from the machine and do the entire setup once more before posted this issue.

I deleted /var/lib/docker several times, just to make sure that I didn't have something mocking me in there from before the upgrade. No joy.

I even tried do change dockers storage storage drive to devicemapper and overlay to see if aufs was causing issues.

@lmakarov
Copy link
Owner

@TLyngeJ try this:

docker rm -f vhost-proxy || true
docker run -d --name vhost-proxy --restart=always --privileged --userns=host \
    -p 192.168.10.10:80:80 -p 192.168.10.10:443:443 \
    -v /var/run/docker.sock:/tmp/docker.sock \
    blinkreaction/nginx-proxy:stable

Restart your project containers with dsh restart, then check docker logs vhost-proxy again.

@TLyngeJ
Copy link
Author

TLyngeJ commented Apr 26, 2016

Yay!

Looks like starting the proxy with the --privileged did the trick.

@lmakarov
Copy link
Owner

lmakarov commented Apr 26, 2016

It's a little more complex than just --privileged.

Starting from docker 1.11.0 user namespaces are enabled by default.
The root user in a container no longer maps to uid=0 on the host.
Both of these become necessary: --privileged --userns=host

More details here:
https://integratedcode.us/2016/04/08/user-namespaces-sharing-the-docker-unix-socket/

@achekulaev
Copy link
Contributor

achekulaev commented May 13, 2016

@lmakarov should we append --privileged --userns=host to dsh?
vhost-proxy only or dns too?

@achekulaev achekulaev added the bug label May 13, 2016
@DigitalFrontiersMedia
Copy link

DigitalFrontiersMedia commented May 23, 2016

I attended the drude bof session at DrupalCon NOLA. I ran into this problem but the solution above doesn't work for me. I'm on a Mac. I get the following:
flag provided but not defined: --userns
Edit: Somehow I'm running Docker 1.10.3. Will upgrade and try again.

@DigitalFrontiersMedia
Copy link

Upgraded to Docker 1.11.1 but now nothing seems right. I'm getting:
Error response from daemon: client is newer than server (client API version: 1.23, server API version: 1.22)

Found this: https://forums.docker.com/t/mismatch-between-api-versions-after-automatic-update-to-1-11-0-beta6-with-docker-machine-on-amazon/8549/5
but when I try the docker-machine upgrade, I get the following:
Error: No machine name(s) specified and no "default" machine exists.
Am I supposed to run it individually on each container created? Starting to get lost in just figuring out how to get this to run.

@lmakarov
Copy link
Owner

lmakarov commented May 23, 2016

@DigitalFrontiersMedia on Mac or Windows you will be running on docker 1.10.3.
Only fresh Linux install are getting the latest docker version when installing, since there is no way to force a particular version install on Linux.

Did you have any previous vagrant, virtualbox or doocker/boot2docker versions installed?

If you did not have anything install previously, then you can try a fresh install/reset of things.
Please do the following in the folder where you initially ran dsh install prerequisites:

vagrant destroy -f
dsh update dsh
dsh update prerequisites
dsh update boot2docker

This should reset you to a "known state".

@davekopecek
Copy link

I was also at the drude bof session at DrupalCon NOLA. I'm having this issue as well.

I'm on Windows. I had a previous installations of VirtualBox, Docker & Vagrant. I uninstalled Docker and Vagrant (but not virtualbox), and removed existing host-only virtualbox adapters. I've created both the drupal7 and drupal8 test projects and am getting the NGINX 503 error on both. I can dsh mysql into the databases and see that they are there, and dsh drush status works. I've tried both master (1.13.3) and the develop branch of dsh

Not sure what logs to look for, etc. Is there a way to inspect the proxy settings?

@DigitalFrontiersMedia
Copy link

Did you have any previous vagrant, virtualbox or doocker/boot2docker versions installed?

I tried cleaning it up before installing drude but must have missed something because I had to uninstall and re-install drude a few times to even get to the 503 stage.

To be clear, I'm running this on a Macbook Pro, OS X 10.11.4 with 4GB RAM (1.5GB free prior to running dsh up), and 340GB of available disk space. I thought perhaps I just did not have enough RAM to run this but Dave is getting very similar results as me and he's running on a beefier Windows laptop, I think.

Output from the above suggested "reset":

MotherPhoenix-3:Projects stephen$ vagrant destroy -f Using nfs2 synced folder option ==> boot2docker: Destroying VM and associated drives... ==> boot2docker: Pruning invalid NFS exports. Administrator privileges will be required... Password: MotherPhoenix-3:Projects stephen$ dsh update dsh Downloading... dsh updated to 1.13.3 MotherPhoenix-3:Projects stephen$ dsh update prerequisites Installing prerequisites... Installing Homebrew... It appears Homebrew is already installed. If your intent is to reinstall you should do the following before running this installer again: ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)" The current contents of /usr/local are bin Cellar CODEOFCONDUCT.md CONTRIBUTING.md cvsrep etc git include info lib Library LICENSE.txt man opt README.md share squid SUPPORTERS.md .git .github .gitignore Updating brew formulae... Already up-to-date. Installing virtualbox... Warning: A Cask for virtualbox is already installed and using auto-updates. Add the "--force" option to force re-install. Installing vagrant... Warning: A Cask for vagrant is already installed. Add the "--force" option to force re-install. Installing docker cli v1.10.3... Password: Installing docker-compose v1.6.2... MotherPhoenix-3:Projects stephen$ dsh update boot2docker Installing boot2docker update... boot2docker 1.5.1 you have is the latest version (-f to force update)

Sometimes if I try to run dsh init from a project directory before running dsh up, I get:
MotherPhoenix-3:drude-d8-testing stephen$ dsh init Initializing local project configuration... /Users/stephen/Projects/drude-d8-testing/docker-compose.yml already in place. /Users/stephen/Projects/drude-d8-testing/docroot/sites/default/settings.local.php already in place. dsh: Unable to connect to the docker daemon

So I run dsh up first, but it seems to pick up on the same init script to install the appropriate project containers. After running dsh up, I can always run dsh init (as seen below). However, both seem to fail and inconsistently. I'll sometimes get different errors each time, like:
ERROR: open /mnt/sda1/var/lib/docker/tmp/GetImageBlob239229443: read-only file system
ERROR: open /mnt/sda1/var/lib/docker/containers/5677faf41d971f5166214867a0a73c6a5aebb3d1c7d71936ccb85d70083cb93c/config.v2.json: read-only file system
ERROR: failed to register layer: rename /mnt/sda1/var/lib/docker/image/aufs/layerdb/tmp/layer-102687668 /mnt/sda1/var/lib/docker/image/aufs/layerdb/sha256/eb9c2ee7bdb7b7029f56d4a98613614fea706225871a4682870d8bd512e25232: directory not empty
ERROR: open /mnt/sda1/var/lib/docker/tmp/GetImageBlob759402497: read-only file system
ERROR: for druded8testing_db_1 Unable to remove filesystem for bd2578633a7a4e0e4b85afe5ca43e54513468ac24fca79557a3ead16e3c5330e: readdirent: input/output error
ERROR: failed to register layer: rename /mnt/sda1/var/lib/docker/image/aufs/layerdb/tmp/layer-058698928 /mnt/sda1/var/lib/docker/image/aufs/layerdb/sha256/c67cae92a5c3deb00f240282cb59584f92be52d789d5a5b5df26f71705110b92: directory not empty
But in every case, I always get:
Error response from daemon: No such container: id Changing user uid in cli from to 502... Error response from daemon: No such container: usermod Reseting permissions on /var/www... Error response from daemon: No such container: chown Restarting php daemon... Error response from daemon: No such container: supervisorctl
And NGINX returns 503.

It appears that not all files download, extract, etc. as necessary before the script moves on or maybe I'm misinterpreting what I'm seeing:
MotherPhoenix-3:Projects stephen$ cd drude-d8-testing/ MotherPhoenix-3:drude-d8-testing stephen$ dsh init Initializing local project configuration... /Users/stephen/Projects/drude-d8-testing/docker-compose.yml already in place. /Users/stephen/Projects/drude-d8-testing/docroot/sites/default/settings.local.php already in place. [!] This will delete all project containers including the DB one. You will have to re-import DB. [y/n]: y Removing containers... No stopped containers Starting containers... Pulling db (blinkreaction/drupal-mysql:5.5)... 5.5: Pulling from blinkreaction/drupal-mysql a3ed95caeb02: Pull complete ffbca234f613: Pull complete b98579aef5c2: Pull complete 550db53f552e: Pull complete 67b618496416: Pull complete 6f17f0e86fa1: Pull complete 8a5d35933de9: Pull complete Digest: sha256:cd1ac2a6d2c1eb97d8c68d36933a2f37b6b1ce2fd0eede8c27f35c99a2f0dd0f Status: Downloaded newer image for blinkreaction/drupal-mysql:5.5 Creating druded8testing_db_1 Pulling cli (blinkreaction/drupal-cli:stable)... stable: Pulling from blinkreaction/drupal-cli fdd5d7827f33: Pull complete a3ed95caeb02: Pull complete 0f35d0fe50cc: Pull complete a3ba689b5187: Pull complete 68ef7c6d5c9d: Pull complete 267b3fab5c0e: Pull complete 0a959973747b: Pull complete 3d968c16eca7: Pull complete 3a26382ec353: Extracting [========================> ] 24.08 MB/49.11 MB b334fce26e50: Download complete 926ea2da60c1: Download complete 53b3c924b723: Download complete af4fd9015f44: Download complete 0958cc5ebdd3: Download complete 8d8ef7382e19: Downloading [==================================================>] 80.52 MB/80.52 MB 1890b8654461: Downloading [==================================================>] 1.7 MB/1.7 MB 3533eaf06f1d: Downloading [==================================================>] 3.257 MB/3.257 MB 31562ba1eaf8: Waiting 0d9f930529e1: Waiting 84dc4c5e2b5a: Waiting 4893101622ca: Waiting 6a7a01b9c346: Waiting 3d80280b61cb: Waiting 13acd9e137b9: Waiting ERROR: open /mnt/sda1/var/lib/docker/tmp/GetImageBlob759402497: read-only file system Error response from daemon: No such container: id Changing user uid in cli from to 502... Error response from daemon: No such container: usermod Reseting permissions on /var/www... Error response from daemon: No such container: chown Restarting php daemon... Error response from daemon: No such container: supervisorctl

When I try to list containers, it acts like there is no docker daemon running:
MotherPhoenix-3:drude-d8-testing stephen$ docker ps Cannot connect to the Docker daemon. Is the docker daemon running on this host?

Yet before I reset the system to a "known state" and I was using Docker 1.11.1, I could get a list and I did not see errors about missing containers--just the "client is newer than server" issue described above.

I've tried resetting this a couple of times. I'm completely lost.

@lmakarov
Copy link
Owner

@DigitalFrontiersMedia looks like you may have a mix of things/versions and the problem is no longer related to vhost-proxy not workin. Please open a separate issue and post the output from the following commands:

VBoxManage --version
vagrant --version
dsh --version
env | grep DOCKER
cat <path/to>/Vagrantfile | grep box_version`
vagrant global-status
docker version
docker-compose version

@lmakarov
Copy link
Owner

@davekopecek what's the URL you are using to access the D7 and D8 test projects?
Should be http://drupal7.drude and http://drupal8.drude respectively.

If you are getting a 503 error from nginx, that means the web containers are either not running or did not register properly with the vhost-proxy.

Please post an output from docker ps (run from anywhere) and dsh ps (run once from both d7 and d8 project folders).

@beeblook
Copy link

beeblook commented May 29, 2016

I've just installed drude on Ubuntu 16.04 and had the same error 403.
Solution by lmakarov fixed the issue, but only for the next

dsh init

@DigitalFrontiersMedia
Copy link

@lmakarov Yes, Dave and I tried several things to troubleshoot my problem and we both arrived at the conclusion that for some reason my laptop gets hung up while cloning the various container files yet the script marches on (after a timeout, I suppose). The script thus tries to set everything up but not all the containers are available. If repeated over and over and over again, it will get farther. But seems to run into a block around the apache container files. The only thing I can think of is that my internet connection or laptop resources aren't able to keep up with all of the clones going on and it fails. It might be nice to add something in the script just before it builds the containers to verify all the files were completely cloned and notify of any failures.

@davekopecek Got his working, btw.

Thanks for helping.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants