Docker for Mac beta - containers do not start

[rnorth]

I think this is potentially, mainly, a Docker for Mac issue, but I'm raising here for visibility and because a fix may be possible on this side.

Here's the issue I've raised in the Docker forums: https://forums.docker.com/t/space-in-new-no-proxy-env-var-breaking-old-containers/14075

In brief:

• Recent versions of Docker for Mac seem to be adding a new environment variable, no_proxy, which contains whitespace: no_proxy=*.local, 169.254/16
• The entrypoint script for the version of selenium containers I have doesn't properly handle spaces environment variables, causing containers to fail to startup:

Waiting xvfb...
-bash: 169.254/16: No such file or directory
Waiting xvfb...
Waiting xvfb...
Waiting xvfb...
Waiting xvfb...
Waiting xvfb...
Waiting xvfb...
Waiting xvfb...
Waiting xvfb...
Waiting xvfb...

To see this, with Docker for Mac beta 13 run:

$ docker run selenium/standalone-chrome-debug:2.52.0 env

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=0d98e7c76683
no_proxy=*.local, 169.254/16
DEBIAN_FRONTEND=noninteractive
DEBCONF_NONINTERACTIVE_SEEN=true
TZ=US/Pacific
SCREEN_WIDTH=1360
SCREEN_HEIGHT=1020
SCREEN_DEPTH=24
DISPLAY=:99.0
CHROME_DRIVER_VERSION=2.20
LANGUAGE=en_US.UTF-8
LANG=en_US.UTF-8
HOME=/root

This line of the entrypoint script seems to need some extra work to deal with spaces in env vars: https://github.com/SeleniumHQ/docker-selenium/blob/master/StandaloneChromeDebug/entry_point.sh#L21

I'll try and submit a patch if I can, but I'd hope the primary fix can be made in the Docker side.

[MartinNuc]

I am having the same issue. Unfortunately overriding it with -e no_proxy="" doesnt work :(

[rnorth]

@MartinNuc actually looking at how I worked around it, I set the no_proxy value to localhost rather than an empty string. Maybe that makes a difference?

On trying to reproduce this tonight, it looks like this has indeed been fixed in Beta 13.1. I now have a version string of: Version 1.11.1-beta13.1 (build: 8193)

This doesn't seem to be injecting a broken no_proxy env var any more.

[philjones88]

I'm on version: Version 1.11.1-beta13.1 (build: 8193) and this issue seems to happen to me. Using the debug version of node-chrome (node-chrome-debug).

[MartinNuc]

I experience this behaviour in Version 1.11.1-beta13.1 (build: 8193).

Using -e no_proxy=localhost has no effect :-(

I am using this command: docker run -d -P -p 5900:5900 --name selenium-node-firefox -e no_proxy=localhost --link selenium-hub:hub selenium/node-firefox-debug:2.53.0

[rnorth]

This is strange - I was launching via an API rather than docker run, so perhaps there's some difference there. I'll go back and try and figure out what's going on!

[rnorth]

@MartinNuc I've checked through the CLI as well as the API - things seem to be working for me setting no_proxy to localhost. My Docker for Mac version string is Version 1.11.1-beta13.1 (build: 8193) e9f58bbe60f0debccc097b7d27cad200556ec6f5...

What do you get from executing these commands:

docker run selenium/standalone-chrome-debug:2.53.0 env

and

docker run -e "no_proxy=localhost" selenium/standalone-chrome-debug:2.53.0 env

?

My output is:

$ docker run selenium/standalone-chrome-debug:2.53.0 env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=39665a2d708e
no_proxy=*.local, 169.254/16
DEBIAN_FRONTEND=noninteractive
DEBCONF_NONINTERACTIVE_SEEN=true
TZ=US/Pacific
SCREEN_WIDTH=1360
SCREEN_HEIGHT=1020
SCREEN_DEPTH=24
DISPLAY=:99.0
CHROME_DRIVER_VERSION=2.21
DBUS_SESSION_BUS_ADDRESS=/dev/null
LANGUAGE=en_US.UTF-8
LANG=en_US.UTF-8
HOME=/root
$ docker run -e "no_proxy=localhost" selenium/standalone-chrome-debug:2.53.0 env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=524027ad54de
no_proxy=localhost
DEBIAN_FRONTEND=noninteractive
DEBCONF_NONINTERACTIVE_SEEN=true
TZ=US/Pacific
SCREEN_WIDTH=1360
SCREEN_HEIGHT=1020
SCREEN_DEPTH=24
DISPLAY=:99.0
CHROME_DRIVER_VERSION=2.21
DBUS_SESSION_BUS_ADDRESS=/dev/null
LANGUAGE=en_US.UTF-8
LANG=en_US.UTF-8
HOME=/root

If I omit the env command, the container starts up when I set no_proxy but fails (with the error above) when I don't set it.

[MartinNuc]

Sorry for late reply. I was sick for few days.

Meanwhile I upgraded to Docker version 1.11.1, build 5604cbe

Tried again -e and indeed it changed env:

docker run -P -p 5900:5900 -e "no_proxy=localhost" --link selenium-hub:hub selenium/node-firefox-debug:2.53.0 env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=18c7ea1a4e19
HUB_PORT=tcp://172.17.0.2:4444
HUB_PORT_4444_TCP=tcp://172.17.0.2:4444
HUB_PORT_4444_TCP_ADDR=172.17.0.2
HUB_PORT_4444_TCP_PORT=4444
HUB_PORT_4444_TCP_PROTO=tcp
HUB_NAME=/drunk_wescoff/hub
HUB_ENV_no_proxy=*.local, 169.254/16
HUB_ENV_GRID_NEW_SESSION_WAIT_TIMEOUT=-1
HUB_ENV_GRID_JETTY_MAX_THREADS=-1
HUB_ENV_GRID_NODE_POLLING=5000
HUB_ENV_GRID_CLEAN_UP_CYCLE=5000
HUB_ENV_GRID_TIMEOUT=30000
HUB_ENV_GRID_BROWSER_TIMEOUT=0
HUB_ENV_GRID_MAX_SESSION=5
HUB_ENV_GRID_UNREGISTER_IF_STILL_DOWN_AFTER=30000
no_proxy=localhost
DEBIAN_FRONTEND=noninteractive
DEBCONF_NONINTERACTIVE_SEEN=true
TZ=US/Pacific
SCREEN_WIDTH=1360
SCREEN_HEIGHT=1020
SCREEN_DEPTH=24
DISPLAY=:99.0
FIREFOX_VERSION=45.0.2
LANGUAGE=en_US.UTF-8
LANG=en_US.UTF-8
HOME=/root

However there is another env with space: HUB_ENV_no_proxy=*.local, 169.254/16 (i am using hub+nodes mode)

So using -e no_proxy=localhost -e HUB_ENV_no_proxy=localhost did the trick :-) Thank you for assistance.

[tommyz0123]

Docker version 1.11.1, build 5604cbe

happen for the debug versions, none debug seems to work fine.

using @MartinNuc trick worked.

[lukeaus]

I had the same problem - setting -e no_proxy=localhost fixes the issue using standalone-firefox-debug:2.52.0 on osx using docker for mac (beta) version 1.12.0-rc2-beta17 (build: 9779)