device mount fails under remote context in MacOS with 19.03.5 docker CLI

BUG REPORT INFORMATION

When i try to do device mount under remote context in MacOS with 19.03.5 docker CLI, i get below error.

$ docker run -d --device=/dev/ttySerial:/dev/ttySerial docker_image
docker: unknown server OS: .
See 'docker run --help'.

Description

Unable to do device mount in 19.03.5 docker cli under remote context. I have setup docker cli to talk to remote docker engine using tcp socket. All the commands work except when running container with some device bind mounted. I didnt see this issue in 18.09.

Steps to reproduce the issue:

1. export DOCKER_HOST=tcp:/<>
2. docker run -d --device=<some_device_on_remote_host> docker_image

Describe the results you received:

docker: unknown server OS: .
See 'docker run --help'.

Describe the results you expected:
I expected the device on the remote host to be mounted successfully into the container.

Output of docker version:

$ docker version
Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.37
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:22:34 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: <---Remote host
 Engine:
  Version:          18.03.0
  API version:      1.37 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       708b068d3095c6a6be939eb2da78c921d2e945e2
  Built:            Fri Dec 13 03:54:50 2019
  OS/Arch:          linux/arm64
  Experimental:     false

Output of docker info:

$ docker info
Client:
 Debug Mode: false

Server:
 Containers: 10
  Running: 7
  Paused: 0
  Stopped: 3
 Images: 1
 Server Version: 18.03.0
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: cfd04396dc68220d1cecbe686a6cc3aa5ce3667c.m (expected: cfd04396dc68220d1cecbe686a6cc3aa5ce3667c)
 runc version: 751f18de2af90495e9c5665b95bfc7adf66ddd57-dirty (expected: 4fc53a81fb7c994640722ac585fa9ca548971871)
 init version: N/A (expected: )
 Security Options:
  userns
 Kernel Version: 4.4.206-armada-17.10.1
 Operating System: <unknown> (containerized)
 OSType: linux
 Architecture: aarch64
 CPUs: 2
 Total Memory: 3.851GiB
 Name: remotedevice
 ID: OF5G:OZRO:WY6E:K3E2:J45I:5ZSE:7ZWO:XJPU:7DQX:MOQS:TVBK:NUHV
 Docker Root Dir: /mnt/xyz/docker/1000000.1000000
 Debug Mode: true
  File Descriptors: 59
  Goroutines: 66
  System Time: 2020-01-22T21:53:35.25600644Z
  EventsListeners: 0
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
Docker cli was run on MacOS with Mojave against remote docker engine on armv8 linux machine.