DNS problem (docker-toolbox \ Win7x64 \ non-admin user)

[John-MEO-o]

Hi,
I've already complete setup & using devilbox tool on OS X
(it means that i understand how it works fine)

But on Windows7 x64 host i have a following issue.
Accordingly to documentation, we need to specify a "LOCAL_LISTEN_ADDR",
which is 127.0.0.1 by default. Docker tools software versions provided in attachment image.
In case of windows 7 we can use only docker-toolbox, and cannot use a docker-native client...
While it starts - it shows an IP 192.168.99.100
which must replace a default IP address (127.0.0.1:) from .env file.

Once I've set that - i'm launching the utility...
Starting procedure are the same as on OS X...
The tool sequentially launches a few web services and goes to idle state...

Afterwards my browser (Google chrome Version 60.0.3112.113 (Official Build) (64-bit))
can't get to the main web-panel, neither one of following addresses are recognized by DNS
127.0.0.1
192.168.99.100
172.16.238.11
localhost

I've tries to set all of them to "LOCAL_LISTEN_ADDR" value,
each time after any changes being made I've erase all present containers through following commands:
docker rm -f $(docker ps -a -q)
docker rmi $(docker images -q)
for now it is still doesn't see web-panel...

Who is sharp enough, please advise - what it can be? Is there any solution for that?
Thanks for paying attention, good luck

Software versions are

Working idle state of devilbox tool

[cytopia]

@jayson-lynnfield-zen unfortunately it is still doesn't support Docker Toolbox. If you have any change to use Windows 10, go for it, otherwise you will have to wait a bit, until I (or someone else) have found a way.

[John-MEO-o]

@cytopia thanks for reply

[cytopia]

@jayson-lynnfield-zen
Could you set LOCAL_LISTEN_ADDR=127.0.0.1: to LOCAL_LISTEN_ADDR= in .env and try to access it again?

By default the devilbox listens on 127.0.0.1, but as Docker Toolbox is an independent VirtualBox (another machine), you want to access it from the outside, so you must allow the devilbox to bind on all interfaces, hence leave the variable empty to accomplish it.

[John-MEO-o]

@cytopia you mean live it blank (empty)?
OK, I'll try, write about it soon

[John-MEO-o]

@cytopia, i've found one weird moment...
Once i've create internal service-dependent directories (www, mysql, pgsql and mongo)
and then get starting devilbox-tool, this folders are not filling by any of temporary working files... is that normal state?

-- My first attempt was a blank address,
such like: LOCAL_LISTEN_ADDR= web-interface inaccessible (output log in attachement)

-- Then i've try to add a colon mark,
like that: LOCAL_LISTEN_ADDR=: fails to start
-- Than i get rid of google's DNS (left only my own DNS Server), and tries to set the my own subnet address with colon-mark at the end,
such as: LOCAL_LISTEN_ADDR=192.168.0.0: web-interface inaccessible...
-- At the final attempt, i've set predefined ip (from router) and its still fails to start
Each time i've erase all containers, just like in documentation.

So maybe i'm getting wrong somewhere of the setup process,
because in OS X internal folders are filled by service-temporary files right after devilbox launches all containers.
My firewall is disabled, no any of AV software being started at that moment.
I'm logged as a standard user (non-admin)

[cytopia]

@jayson-lynnfield-zen can you paste the full log for httpd from your first try with an empty LOCAL_LISTEN_ADDR (no colon):

docker-compose up -d
docker-compose logs httpd

[John-MEO-o]

@cytopia yep, I'll send it, when get to the pc...
Through 4-5 hours or so

[John-MEO-o]

@cytopia i've execute that,results are below

[cytopia]

@jayson-lynnfield-zen I made a major rewrite to overcome some limitations. I hope I could also address your problems. Pull request is not merged yet (#130), however could you checkout the branch (REL-0.12) and give it a try:

1. just to make sure everything is reset

docker-compose down
docker-compose rm -f

2. Check out new branch

git fetch --all
git checkout REL-0.12

3. Compare new env-example with your local .env

vimdiff .env env-example

4. Start it up

docker-compose up -d

Hope it can fix some problems

[John-MEO-o]

Thanks man, I'll check it as fast as I can, write you later Best regards, Jason E. Отправлено из ProtonMail mobile

…

-------- Исходное сообщение -------- Вкл 28 сент. 2017 г., 2:26, cytopia написал(а):

***@***.***(https://github.com/jayson-lynnfield-zen) I made a major rewrite to overcome some limitations. I hope I could also address your problems. Pull request is not merged yet ([#130](#130)), however could you checkout the branch and give it a try: - just to make sure everything is reset docker-compose down docker-compose rm -f - Check out new branch git fetch --all git checkout REL-0.12 - Compare new env-example with your local .env vimdiff .env env-example - Start it up docker-compose up -d Hope it can fix some problems — You are receiving this because you were mentioned. Reply to this email directly, [view it on GitHub](#119 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AZjY4Gm8-WoL7mjm9gXUiqsv_9QEMbEzks5smr12gaJpZM4PGkxi).

[John-MEO-o]

@cytopia
I've downloaded latest version, it gives an error right from starting... (See attached file)
i've set dns server to my own, than to Google's, afterwards i change IP to null, and to docker-toolbox IP with no any results. Firewall was disabled.

[cytopia]

@jayson-lynnfield-zen

There seems to be two docker networks. One from your previous devilbox instance and the new one. However both do use the same IP.

So do the following (First shutdown the devilbox):

# show devilbox networks
docker network ls --filter 'name=devil*' 

# delete all networks starting by devilbox
docker network rm <network-name>

Alternatively use this command:

docker network rm $(docker network ls --filter 'name=devil*' -q | xargs)

That should fix your problems