Dory seems to be trying to access the wrong service

[rmNyro]

It's me again, I'll get you (if not already ^^) tired of reading my issues if I continue so I'll try to avoid problems in the future, I swear. But as for now, dory doesn't want to talk to my app.

It's very very strange. I tried dory for the first time with nightwatch-docker-grid and it worked (except that any .docker terminated url matches the helloworld container used in the project as explained on #13 (comment)). But when I run my project, dory tries to access the wrong service from the container.

My compose file is pretty simple and looks like:

version: '2'

volumes:
    mongo-volume:

services:
    main_service:
        build: .
        volumes:
            - ../src:/var/www/app
        environment:
            STATE: dev
            WEBROOT: /var/www/app
            VIRTUAL_HOST: custom-url.docker
        depends_on:
          - mongo_service

    mongo_service:
        image: mongo:3.5
        volumes:
            - mongo-volume:/data/db

Now an image showing all of the containers on my machine after launching

and wherever I put VIRTUAL_HOST, dory still tries to access mongo_service resulting in:

mongo_service_1    | 2017-08-29T14:05:39.560+0000 I NETWORK  [conn6] Error receiving request from client: SSLHandshakeFailed: SSLHandshakeFailed. Ending connection from 172.18.0.3:49812 (connection id: 6)
mongo_service_1    | 2017-08-29T14:05:39.560+0000 I NETWORK  [conn6] end connection 172.18.0.3:49812 (3 connections now open)

although it should be main_service_1 which should be receiving the request.

My confusion is at its highest and I'm sadly forced to back down on dory and return to old dirt /etc/hosts editting which is bad bad bad because docker changes ip all the time...

P.S.: my environment is the same since #13 (comment)

[FreedomBen]

Sounds like probablyl same root issue as #13

(see #13 (comment) )

[jhoogeboom]

Were you able to fix this @rmNyro ?

[rmNyro]

Unfortunatly no @jhoogeboom, it's been a while since I had this issue but I don't recall trying to make it work and it did not seem to be a permission issue neither.