-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOCKER_HOST is not respected #84
Comments
It seems that this bug was fixed in v2.0.0a3 pre-release, but that was like more than 6 months ago. Maybe it would make sense to tag a release. |
Ugh, sorry about that. I meant to cut the release ... many months ago. 2020 caught up with me. Anyway, https://github.com/tox-dev/tox-docker/releases/tag/v2.0.0 is out the door and https://pypi.org/project/tox-docker/2.0.0/ is published. Let me know if this bug still exists on 2.0, but it seems like it shouldn't. |
I have a similar issue in the latest 3.0.0 release. In CircleCI (and others) DOCKER_HOST is set to the remote docker:
But running tox with tox-docker yields the standard Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. It would appear that docker.from_env isn't honouring default settings, in our context. In case it helps, here's the output of my poetry.lock, after a fresh install - with nothing pinned.
It goes without saying that docker ps runs properly. |
This happens with 2.0.0 as well. |
How are you running tox? |
Standard command line run (tox -e ) via a virtualenv. |
I wonder if something is preventing the env var from getting through. DOCKER_HOST should work as expected. Could you try using |
I do have a
DOCKER_HOST=ssh://[email protected]
which is correctly used by all docker tools, including the docker-py python library. Still, tox-docker does not seem to rely on it and fails to run, thorwin an exception like:From the same machine doing a
docker pull
worked without any problems.The text was updated successfully, but these errors were encountered: