-
Notifications
You must be signed in to change notification settings - Fork 37
vhost-proxy appears to have stopped working correctly #105
Comments
I've not yet tested Drude/Docker with Ubuntu 16.04.
Try running |
|
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 I even tried do change dockers storage storage drive to devicemapper and overlay to see if aufs was causing issues. |
@TLyngeJ try this:
Restart your project containers with |
Yay! Looks like starting the proxy with the |
It's a little more complex than just Starting from docker 1.11.0 user namespaces are enabled by default. More details here: |
@lmakarov should we append |
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: |
Upgraded to Docker 1.11.1 but now nothing seems right. I'm getting: 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 |
@DigitalFrontiersMedia on Mac or Windows you will be running on docker 1.10.3. 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.
This should reset you to a "known state". |
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 Not sure what logs to look for, etc. Is there a way to inspect the proxy settings? |
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":
Sometimes if I try to run dsh init from a project directory before running dsh up, I get: 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: 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: When I try to list containers, it acts like there is no docker daemon running: 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. |
@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:
|
@davekopecek what's the URL you are using to access the D7 and D8 test projects? 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 |
I've just installed drude on Ubuntu 16.04 and had the same error 403.
|
@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. |
I just update my Ubuntu OS:
I also update
dsh
: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: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:
I believe that I am using the latest image versions:
And if it's any use to you, this is a
docker inspect
on thenginx-proxy
container:The text was updated successfully, but these errors were encountered: