docker-compose versions 1.10.1 and 1.11.1 (docker-py version 2.0.2) fails on command "build" with the following stack trace: Traceback (most recent call last): File "/usr/lib/python-exec/python3.4/docker-compose", line 11, in <module> load_entry_point('docker-compose==1.11.1', 'console_scripts', 'docker-compose')() File "/usr/lib64/python3.4/site-packages/compose/cli/main.py", line 88, in main command() File "/usr/lib64/python3.4/site-packages/compose/cli/main.py", line 140, in perform_command handler(command, command_options) File "/usr/lib64/python3.4/site-packages/compose/cli/main.py", line 247, in build force_rm=bool(options.get('--force-rm', False))) File "/usr/lib64/python3.4/site-packages/compose/project.py", line 313, in build service.build(no_cache, pull, force_rm) File "/usr/lib64/python3.4/site-packages/compose/service.py", line 804, in build buildargs=build_opts.get('args', None), File "/usr/lib64/python3.4/site-packages/docker/api/build.py", line 139, in build path, exclude=exclude, dockerfile=dockerfile, gzip=gzip File "/usr/lib64/python3.4/site-packages/docker/utils/utils.py", line 105, in tar t.addfile(i, f) File "/usr/lib64/python3.4/tarfile.py", line 1952, in addfile buf = tarinfo.tobuf(self.format, self.encoding, self.errors) AttributeError: 'NoneType' object has no attribute 'tobuf' The problem was not appearing previously with docker-py==1.10.6, but the previous docker-compose versions lack some features I need. The whole situation looks like a bug in docker-py 2.x.
Created attachment 464110 [details] emerge --info output
Seems to be my fault: https://github.com/docker/compose/issues/4363
Sorry :\