FS#57546 - [docker-compose] Not compatible with python-docker 3.0.1
Attached to Project:
Community Packages
Opened by Devin Samarin (dsamarin) - Saturday, 17 February 2018, 12:15 GMT
Last edited by Felix Yan (felixonmars) - Saturday, 17 February 2018, 17:49 GMT
Opened by Devin Samarin (dsamarin) - Saturday, 17 February 2018, 12:15 GMT
Last edited by Felix Yan (felixonmars) - Saturday, 17 February 2018, 17:49 GMT
|
Details
With python-docker-3.0.1, docker-compose up produces:
$ docker-compose up Building service Traceback (most recent call last): File "/usr/bin/docker-compose", line 11, in <module> load_entry_point('docker-compose==1.19.0', 'console_scripts', 'docker-compose')() File "/usr/lib/python3.6/site-packages/compose/cli/main.py", line 71, in main command() File "/usr/lib/python3.6/site-packages/compose/cli/main.py", line 124, in perform_command handler(command, command_options) File "/usr/lib/python3.6/site-packages/compose/cli/main.py", line 1001, in up to_attach = up(False) File "/usr/lib/python3.6/site-packages/compose/cli/main.py", line 997, in up renew_anonymous_volumes=options.get('--renew-anon-volumes') File "/usr/lib/python3.6/site-packages/compose/project.py", line 463, in up svc.ensure_image_exists(do_build=do_build) File "/usr/lib/python3.6/site-packages/compose/service.py", line 326, in ensure_image_exists self.build() File "/usr/lib/python3.6/site-packages/compose/service.py", line 989, in build 'memory': parse_bytes(memory) if memory else None TypeError: build() got an unexpected keyword argument 'stream' The problem is fixed with: $ sudo pacman -U /var/cache/pacman/pkg/python-docker-2.7.0-1-any.pkg.tar.xz |
This task depends upon
Closed by Felix Yan (felixonmars)
Saturday, 17 February 2018, 17:49 GMT
Reason for closing: Fixed
Additional comments about closing: 1.19.0-2
Saturday, 17 February 2018, 17:49 GMT
Reason for closing: Fixed
Additional comments about closing: 1.19.0-2
Comment by
Felix Yan (felixonmars) - Saturday,
17 February 2018, 17:32 GMT
Comment by
Iván Perdomo (katratxo) - Saturday,
17 February 2018, 17:48 GMT
Please let me know if 1.19.0-2 addresses this.
Many thanks for the quick response. This solves the problem.