search

FreedomBen / dory

Your development proxy for docker
MIT License
156 stars 24 forks source link

Dory seems broken on Mint #13

Open rmNyro opened 7 years ago

rmNyro commented 7 years ago

Hi again,

I completely lost so I'm quickly posting to tell what's what's but I might be too much concise. I'm testing dory on Linux Mint 18.1 Serena as you now know. I have no container (before running any test obviously) running except for portainer and dory: dory status

The first strange thing is that the domain name doesn't really matter. i.e.: docker run -it -e VIRTUAL_HOST=s -e VIRTUAL_PORT=8000 crccheck/hello-world can be accessed via http://fgsdg.docker/ or anything ending with .docker. I suppose it is not exactly the desired behavior (or is it?).

The second problem is that only DN ending by .docker are accessible from the browser. If another server has another custom fancy DN, it's inaccessible (the first launched gets the response) because of that. So to access it, you have to specify a "correct" DN ending with .docker.

Sooooo, is my Mint a hater to dory? I have no background in ruby and very little in DevOps/networking so I'm afraid I can't quite help but to report. :/

And again, I hope it helped. :)

EDIT: I forgot to put version of ruby and dory so here it is

➜  ~ ruby -v
ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]
➜  ~ dory -v
/var/lib/gems/2.3.0/gems/dory-0.6.2/lib/dory/version.rb:2: warning: already initialized constant Dory::VERSION
/var/lib/gems/2.3.0/gems/dory-0.6.3/lib/dory/version.rb:2: warning: previous definition of VERSION was here
/var/lib/gems/2.3.0/gems/dory-0.6.2/lib/dory/version.rb:3: warning: already initialized constant Dory::DATE
/var/lib/gems/2.3.0/gems/dory-0.6.3/lib/dory/version.rb:3: warning: previous definition of DATE was here
Dory - Version: 0.6.2

I must say I didn't see those warnings but I'm pretty sure it has nothing to do with my problem.

FreedomBen commented 7 years ago

Yep, the warning are not related (and I'll try to fix those soon cause they're annoying).

I have seen this before, but it's really hard to reproduce. It seems like the docker networking and the proxy container get into some weird state where they don't behave properly. Each time one of the following seems to fix it:

  1. Restart docker (this will kill dory's docker containers, so need to start dory again after):

    sudo systemctl restart docker
dory up

  2. Double check VIRTUAL_HOST variables and VIRTUAL_PORT. Sometimes if the downstream container isn't reachable the nginx proxy will pick one as a "default." The unreachability can be caused by little typos in host or port.

  3. Attach to the proxy, then restart your application containers and make sure you see the output:

dory attach proxy  # this will take over the current terminal, so run next commands in separate terminal windows
docker-compose down
docker-compose up