Running a container like docker-compose -p "cutter" up will output:
base_theme_builder | g changed files to targets
base_theme_builder | ##teamcity[progressMessage 'Applying changes']
base_theme_builder | ty[progressMessage 'Waiting for containers to stop']
base_theme_builder | h exited 0
base_theme_builder | nish.d] executing container finish scripts...
base_theme_builder | nish.d] done.
base_theme_builder | sh] syncing disks.
base_theme_builder | sh] sending all processes the TERM signal.
base_theme_builder | sh] sending all processes the KILL signal and exiting.
However, running docker-compose -p "cutter" up -d and viewing the logs:
base_theme_builder | Copying changed files to targets
base_theme_builder | ##teamcity[progressMessage 'Applying changes']
base_theme_builder | ##teamcity[progressMessage 'Waiting for containers to stop']
base_theme_builder | /bin/bash exited 0
base_theme_builder | [cont-finish.d] executing container finish scripts...
base_theme_builder | [cont-finish.d] done.
base_theme_builder | [s6-finish] syncing disks.
base_theme_builder | [s6-finish] sending all processes the TERM signal.
base_theme_builder | [s6-finish] sending all processes the KILL signal and exiting.
I will get together a sample repo, but hopefully others can reproduce this easily in the meantime.
This has been since 1.8.0.
Might be related to docker/docker-py#1250
Just had a very strange experience where the cutoff was in the middle of control characters for color and affected my system (printed out my console session to the printer -- all 400 pages of it). Please fix this 🔜
Also seeing this when it catches these control characters:
Traceback (most recent call last):
File "<string>", line 3, in <module>
File "compose/cli/main.py", line 65, in main
File "compose/cli/main.py", line 117, in perform_command
File "compose/cli/main.py", line 862, in up
File "compose/cli/log_printer.py", line 87, in run
File "compose/cli/log_printer.py", line 229, in consume_queue
OverflowError: signed integer is greater than maximum
docker-compose returned -1```
Hi @withinboredom ,
Is this still an issue with more recent versions of Compose? https://github.com/docker/docker-py/pull/1250 should have fixed it.
I haven't seen it lately. Close away!
On Mon, Apr 10, 2017, 9:43 PM Joffrey F notifications@github.com wrote:
Hi @withinboredom https://github.com/withinboredom ,
Is this still an issue with more recent versions of Compose?
docker/docker-py#1250 https://github.com/docker/docker-py/pull/1250
should have fixed it.—
You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub
https://github.com/docker/compose/issues/4027#issuecomment-293125673,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABy8oPDsKjAeNxfPJMxWF9ufFFmD6Wm5ks5rutrUgaJpZM4KT5IG
.>
Robert Landers
Software Engineer
Charleston, SC, USA
Thank you!
Most helpful comment
Also seeing this when it catches these control characters:
Traceback (most recent call last): File "<string>", line 3, in <module> File "compose/cli/main.py", line 65, in main File "compose/cli/main.py", line 117, in perform_command File "compose/cli/main.py", line 862, in up File "compose/cli/log_printer.py", line 87, in run File "compose/cli/log_printer.py", line 229, in consume_queue OverflowError: signed integer is greater than maximum docker-compose returned -1```