Ivan

@NorseGaud @urbantrout Actually, the problem is here: `$( [ -n "$(sw_vers | grep 10.14)" ] && echo ",nfsvers=3 ")` Here is screenshot from Travis build:  Probably, it would be...

It seems, the problem is in boot2docker.iso So, the solution works for me: 1. Download previous version of boot2docker.iso: https://github.com/boot2docker/boot2docker/releases/tag/v19.03.5 2. Put the file to the `$HOME/.docker/machine/cache/boot2docker.iso` 2. Turn off...

@MuhmdRaouf Hi! I don't think it's a good idea but I attached binary and created release 0.4.1 in my fork so you can try it: https://github.com/iworker/docker-machine-driver-xhyve/releases/tag/v0.4.1 But I still think...

@jaequery Hi Did you try the second part of my instruction? There is a problem with using 4th version of NFS driver, so I did a [commit](https://github.com/iworker/docker-machine-driver-xhyve/commit/8f53351cfcc3794c688211fc20f178208e8c3c16) with forced using...

> @iworker thanks. anyway we can get this resolved without resorting to this type of workaround? because, i think this is currently broken for everyone at this point, as i...

Probably better give an ability to use Google reverse geocoding or Yandex.Maps reverse geocoding?

@lodgnewt @WhiteBearSpirit it seems that docker image is not updated: https://hub.docker.com/r/ex3ndr/telegram-proxy/ So you can just build it by yourself and use your own build: ``` docker build -t telegram-proxy ....

You can change port when you start docker container. Like `docker run --restart always -d --name telegram-proxy -p 2345:1080 ex3ndr/telegram-proxy` for port 2345.

Also it's better to use MTProto proxy. Instruction is available here: https://habr.com/post/412755/

Using it without docker looks like exceptional case. But if you really want to, this PR makes sense.