Node-chrome 3.14.0 docker swarm service not starting

[JordiGiros]

Meta -

Image(s):

Docker-Selenium Image Version(s): 3.14.0 (latest)

Docker Version: Docker version 17.05.0-ce, build 89658be

OS: Ubuntu 16.04

Expected Behavior -

Node-chrome service in swarm mode should start normally and connect to hub.

Actual Behavior -

Node-chrome service in swarm mode fails giving an error.
"Err": "task: non-zero exit (127)",

Steps to reproduce -

Start a swarm

sudo docker swarm init --force-new-cluster
sudo docker network create --driver overlay back
sudo docker stack deploy --compose-file ~/docker-selenium.yml selenium

docker-selenium.yml:
version: '3'

services:
  hub:
    image: selenium/hub:latest
    ports:
      - "4444:4444"
    deploy:
     mode: global
     placement:
       constraints:
         - node.role == manager
    environment:
     - GRID_BROWSER_TIMEOUT=0
     - GRID_TIMEOUT=60000
     - GRID_MAX_SESSION=50
     - GRID_MAX_INSTANCES=20
     - GRID_CLEAN_UP_CYCLE=60000
     - GRID_UNREGISTER_IF_STILL_DOWN_AFTER=180000
     - GRID_NEW_SESSION_WAIT_TIMEOUT=60000
    networks:
     - back
    deploy:
      mode: replicated
      replicas: 1
      resources:
        limits:
          memory: 2048M
        reservations:
          memory: 512M

  chrome:
    image: selenium/node-chrome:latest
    volumes:
      - /dev/shm:/dev/shm
    depends_on:
      - hub
    environment:
      - HUB_PORT_4444_TCP_ADDR=hub
      - HUB_PORT_4444_TCP_PORT=4444
      - NODE_MAX_SESSION=1
      - GRID_CLEAN_UP_CYCLE=60000
      - NODE_MAX_SESSION=5
      - NODE_MAX_INSTANCES=5
    entrypoint: bash -c 'SE_OPTS="-host $$HOSTNAME -port 5556 -browserTimeout 600 -sessionTimeout 600" /opt/bin/entry_point.sh'
    ports:
      - "5556:5556"
    deploy:
      replicas: 1
    networks:
      - back
    deploy:
      mode: replicated
      replicas: 1
      resources:
        limits:
          memory: 2048M
        reservations:
          memory: 512M

networks:
  back:
    external: true

node-version 3.13.0 works fine.

[elemenophy]

This is a duplicate of #800 for sure.

Check your chrome log, and you will see a message saying that it can't find /opt/bin/entry_point.sh

[diemol]

Fixed in the referenced commit and will be released soon.

[PramodDutta]

Fixed in the referenced commit and will be released soon.

Diemol You... saviour 👍

[diemol]

Credits to @ay0o for pointing the solution.