Hey, this is pretty sweet.<p>This is a simple alternative than the solution I wrote about here: <a href="https:&#x2F;&#x2F;allysonjulian.com&#x2F;setting-up-docker-with-xhyve&#x2F;" rel="nofollow">https:&#x2F;&#x2F;allysonjulian.com&#x2F;setting-up-docker-with-xhyve&#x2F;</a> which uses docker-machine-driver-xhyve (<a href="https:&#x2F;&#x2F;github.com&#x2F;zchee&#x2F;docker-machine-driver-xhyve" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;zchee&#x2F;docker-machine-driver-xhyve</a>).<p>I&#x27;ve been trying to figure out how to deal with the env variables used by docker, and used a workaround ~&#x2F;.profile (<a href="https:&#x2F;&#x2F;gist.github.com&#x2F;astrohckr&#x2F;efceb07887225cbc2ba2" rel="nofollow">https:&#x2F;&#x2F;gist.github.com&#x2F;astrohckr&#x2F;efceb07887225cbc2ba2</a>). Like the OP, running eval in every terminal session makes me a bit concerned as well.<p>I&#x27;ll give dlite a Go.