Fix parsing of docker-compose output.

[GrahamDennis]

Before this PR

Newer versions of docker-compose (at least 1.25.0-rc4) adjust the output based on the number of columns available in the terminal. This interferes with parsing of the output and can cause errors like "No internal port X for container Y" when the port does exist. This is because of a parse failure while parsing the output of docker-compose ps.

After this PR

==COMMIT_MSG==
Set the COLUMNS environment variable to an artificially large value for the docker-compose process. This works around newer versions of docker-compose (at least 1.25.0-rc4+) which adjust their output based on the width of the terminal.
==COMMIT_MSG==

[changelog-app]

Generate changelog in changelog/@unreleased

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Set the COLUMNS environment variable to an artificially large value for the docker-compose process. This works around newer versions of docker-compose (at least 1.25.0-rc4+) which adjust their output based on the width of the terminal.

Check the box to generate changelog(s)

• Generate changelog entry

[CRogers]

Thanks for the PR. #418 also aims to fix this same problem and will do port parsing in a more sensible way (than parsing ps output). I still need to review it though, as it's a much larger change, so I'm happy to merge this now to fix the immediate issue.

[svc-autorelease]

Released 1.4.2

[GrahamDennis]

@CRogers: thanks! Note that the past few releases aren't getting published by Circle. It seems like the builds are getting stuck. See https://circleci.com/gh/palantir/docker-compose-rule/5316