Open rmNyro opened 7 years ago
Sounds like probablyl same root issue as #13
(see https://github.com/FreedomBen/dory/issues/13#issuecomment-326693298 )
Were you able to fix this @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.
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 https://github.com/FreedomBen/dory/issues/13#issue-253669416). 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:
Now an image showing all of the containers on my machine after launching and wherever I put
VIRTUAL_HOST
, dory still tries to accessmongo_service
resulting in: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 https://github.com/FreedomBen/dory/issues/13#issue-253669416