-
Notifications
You must be signed in to change notification settings - Fork 394
UnixHTTPConnectionPool(host='localhost', port=None): Pool is closed #261
Comments
Pushed a new ansible/ansible-container-builder:0.2 to Docker Hub just a few minutes ago. Here's what is actually installed:
@ReeSilva can you confirm if this fixes the issue you're seeing? |
@chouseknecht I will try it on my next builds and see if error occur again. Does ansible-container is already using ansible-container-builder:0.2? I'm using ansible-container from pip version, once we use this to build our staging containers. |
To use the 0.2 container, you will need to install from source, not from pip. |
@chouseknecht Ok. On the 0.2 Ansible Container will change anything about how I call my playbooks or I prepare my environment to run Ansible-Container? Because if I have to rewrite this I belive that u guys still don't have docs to explain, and I will lost sometime to find out how to do. But, if there is no change in this stuffs and I can run Ansible Container with my files the way they are now, I'll give a try. In other way, if I have to change something I'll wait for the release on pip. |
You should not need to change anything. In version 0.2 we have been fixing bugs and adding new features. I can't think of anything that got removed or redefined. Of course, if this is a production process, I would recommend testing, just to make sure I'm not forgetting something. |
@chouseknecht Nice to know. So tomorrow I'll give a try and test. If everything works well, I'll implement. Thanks a lot. |
Still getting the error even with the new version. This is an error with docker-compose, that was fixed on 1.8.1 (docker/compose#3586)
|
Hmmm... we're installing docker in the ansible/ansible-container-builder:0.2 image, because we need the client pieces. We install the latest available RPM which is 1.12.1. It looks like that was released around August 18, so it would not have this change. The next release after that is 1.12.2-rc1. Not sure where to get the RPM for that, but it's probably available. What you could is...
|
Does docker-compose comes with docker-latest? |
You get the docker-compose CLI tool. It doesn't install the python module, but presumably whatever fixes are baked into the python somehow end up in the CLI. That's my assumption. |
Docker Compose is run from outside of the build container in Ansible Container itself. The requirement is defined here: https://github.com/ansible/ansible-container/blob/develop/requirements.txt#L1 |
Ugh. Totally missed that. Is there any reason to not bump this to 1.8.1 and just let it install the latest docker-py? |
I have same problem on commiting large size docker container. |
It would be really great if we could change timeout via environment variable (likely done in here) b/c right now it's hardcoded. |
@TomasTomecek |
Working on upgrading to latest docker-py and docker-compose libraries: #314. PR in place here: #316 Thinking we really need docker/compose#4090 resolved before we merge, even though all tests are passing. |
If you need to set a longer timeout for the docker client, the develop branch now respects DOCKER_CLIENT_TIMEOUT and COMPOSE_HTTP_TIMEOUT. |
I had the same error when starting docker with log-driver: syslog when rsyslog port was unavailable. |
ISSUE TYPE
SUMMARY
When we have a high number of containers, Docker Compose exceed the limit of connection pool. This was fix on recently released docker-compose, but Ansible Container still uses Docker Compose.
If possible this could be changed on the actual version of Ansible Container, once this can block of use who have a lot of containers.
STEPS TO REPRODUCE
Create an structure with more than 20 containers.
Try to run Ansible-container.
References
docker/compose#3586
https://github.com/docker/compose/releases/tag/1.8.1
The text was updated successfully, but these errors were encountered: