Unable to create a new session on a new Docker version (API 1.38)

[sskorol]

Docker API: 1.38
Version 18.06.0-ce-rc3-mac68 (26342)
Channel: edge
OS: Mac OS High Sierra 10.13.5
Selenoid: 1.7.0

browsers.json

{
	"chrome": {
		"default": "66.0",
		"versions": {
			"66.0": {
				"image": "selenoid/vnc:chrome_66.0",
				"port": "4444"
			}
		}
	},
	"firefox": {
		"default": "61.0",
		"versions": {
			"61.0": {
				"image": "selenoid/vnc:firefox_61.0",
				"port": "4444"
			}
		}
	}
}

docker-compose.yml

version: '3.6'
services:
  selenoid:
    image: "aerokube/selenoid:latest-release"
    ports:
      - "4444:4444"
    volumes:
      - "$PWD:/etc/selenoid"
      - "//var/run/docker.sock:/var/run/docker.sock"
    command: ["-conf", "/etc/selenoid/browsers.json", "-container-network", "docker_automation"]
    networks:
      - automation
  selenoid-ui:
    image: "aerokube/selenoid-ui:latest-release"
    depends_on:
      - selenoid
    ports:
      - "8080:8080"
    command: ["--selenoid-uri", "http://selenoid:4444"]
    networks:
      - automation
networks:
  automation:
    driver: bridge

Step: navigate to any URL via Selenium API
Expected: browser is opened and redirected to specified URL.
Actual: session is failing by timeout: ERROR: New session attempts retry count exceeded

Logs:

2018/07/21 12:51:16 [-] [INIT] [Loading configuration files...]
2018/07/21 12:51:16 [-] [INIT] [Loaded configuration from /etc/selenoid/browsers.json]
2018/07/21 12:51:16 [-] [INIT] [Using default containers log configuration because of: read error: open config/container-logs.json: no such file or directory]
2018/07/21 12:51:16 [-] [INIT] [Video Dir: /opt/selenoid/video]
2018/07/21 12:51:16 [-] [INIT] [Did not manage to determine your Docker API version - using default version: 1.37]
2018/07/21 12:51:16 [-] [INIT] [Timezone: Local]
2018/07/21 12:51:16 [-] [INIT] [Listening on :4444]
2018/07/21 12:51:35 [-] [NEW_REQUEST] [unknown] [172.18.0.1]
2018/07/21 12:51:35 [-] [NEW_REQUEST_ACCEPTED] [unknown] [172.18.0.1]
2018/07/21 12:51:35 [0] [LOCATING_SERVICE] [chrome] [66.0]
2018/07/21 12:51:35 [0] [USING_DOCKER] [chrome] [66.0]
2018/07/21 12:51:35 [0] [CREATING_CONTAINER] [selenoid/vnc:chrome_66.0]
2018/07/21 12:51:36 [0] [STARTING_CONTAINER] [selenoid/vnc:chrome_66.0] [b0e659d6f3aa1dcd93e3fc2b8c5099f7800ae3086bfa0537c18184ab95ca75a0]
2018/07/21 12:51:36 [0] [CONTAINER_STARTED] [selenoid/vnc:chrome_66.0] [b0e659d6f3aa1dcd93e3fc2b8c5099f7800ae3086bfa0537c18184ab95ca75a0] [0.43s]
2018/07/21 12:51:36 [0] [SERVICE_STARTED] [selenoid/vnc:chrome_66.0] [b0e659d6f3aa1dcd93e3fc2b8c5099f7800ae3086bfa0537c18184ab95ca75a0] [0.00s]
2018/07/21 12:51:36 [0] [PROXY_TO] [b0e659d6f3aa1dcd93e3fc2b8c5099f7800ae3086bfa0537c18184ab95ca75a0] [http://:4444]
2018/07/21 12:51:36 [0] [SESSION_ATTEMPTED] [http://:4444] [1]
2018/07/21 12:51:36 [0] [SESSION_ATTEMPTED] [http://:4444/wd/hub] [2]
2018/07/21 12:51:36 [-] [NEW_REQUEST] [unknown] [127.0.0.1]

Root cause: Did not manage to determine your Docker API version - using default version: 1.37

[sskorol]

@vania-pooh would be greatly appreciated if you update a client.

[vania-pooh]

@sskorol ok, this is reproducing with custom networks only. Old releases work like a charm in default network. Let's see whether Docker client update will fix the issue.

[vania-pooh]

@sskorol should work with aerokube/selenoid:latest.

[tigranvardanyan15]

As a workaround you can get docker API version with docker version and then expose version with command:
export DOCKER_API_VERSION='<version>'