Created attachment 584476 [details] Trace of docker-compose up -d I've upgraded docker-compose from 1.19 to 1.24.0, but I had to upgrade manually dev-python/paramiko from 2.4.1 to 2.4.1 else docker-compose up -d resulted in a dependency conflict error.
As far as I can see from the log this is an issue with dev-python/docker-py which needs paramiko >=2.4.2 from 3.6.0 on but depends on plain "dev-python/paramiko[${PYTHON_USEDEP}]" which is a problem with your old 2.4.1 around but sort-of-correct if one pulls the card that only in-tree dependencies are considered and supported. So we have two options in my view: a) Encode >=2.4.2 in the dependencies of dev-python/docker-py b) Consider this case as unsupported as it affects outdated systems, only. I'd be good with either, handing over to the maintainer of dev-python/docker-py for now.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a68e9af462401d97f8e924e0d58b8995eba57196 commit a68e9af462401d97f8e924e0d58b8995eba57196 Author: Sebastian Pipping <sping@gentoo.org> AuthorDate: 2019-11-23 16:26:40 +0000 Commit: Sebastian Pipping <sping@gentoo.org> CommitDate: 2019-11-23 16:26:40 +0000 dev-python/docker-py: >=3.6.0 needs paramiko >=2.4.2 Closes: https://bugs.gentoo.org/690700 Signed-off-by: Sebastian Pipping <sping@gentoo.org> Package-Manager: Portage-2.3.78, Repoman-2.3.16 dev-python/docker-py/docker-py-3.6.0.ebuild | 2 +- dev-python/docker-py/docker-py-3.7.1.ebuild | 2 +- dev-python/docker-py/docker-py-3.7.3.ebuild | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)