docker: poorly formatted environment:variable in travis (TRAVIS_COMMIT_MESSAGE)

• Version: 19.49.2

• Target: Windows and Linux using Docker.

While building for windows and linux using docker on trusty environment in travis, i am getting this error:

docker: poorly formatted environment: variable 'Refactored Settings system by moving it from dexie to JSON. Results in less complexity and efficiency as listeners are removed.' has white spaces.

I have used the travis config as provided in the docs sample project. The builds were running fine with the same config before. Between the last successful build and the current build, the .travis.yml file has not been touched at all.

The mac builds are working perfectly, so I assume the error is due to some config issue.

[Clover-Lindo]

@xsokaris I found another way here https://github.com/moby/moby/issues/12997#issuecomment-307665540

Here’s my full script:

  npm run build:prod
  ENVS=`env | grep -iE '^(DEBUG|NODE_|ELECTRON_|YARN_|NPM_|CI|CIRCLE|TRAVIS|APPVEYOR_|CSC_|_TOKEN|_KEY|AWS_|STRIP|BUILD_)([A-Z]|_)*=' | sed -n '/^[^\t]/s/=.*//p' | sed '/^$/d' | sed 's/^/-e /g' | tr '\n' ' '`
  if [ "$TRAVIS_OS_NAME" == "linux" ]; then
    docker run $ENVS --rm \
      -v ${PWD}:/project \
      -v ~/.cache/electron:/root/.cache/electron \
      -v ~/.cache/electron-builder:/root/.cache/electron-builder \
      electronuserland/builder:wine \
      /bin/bash -c "npm run release:linux && npm run release:win"
  else
    npm run release:mac
  fi

Istead of passing vars with --env-file, it creates a list of -e VAR1 -e VAR2, and docker will be able to find the value of each itself. I also fixed the regex so it only takes vars starting by, and not only containing “DEBUG”, “NODE_” etc.

Eventually you’ll have to add your environment variable pattern if it is not already matched by the regular expression.

[Clover-Lindo]

(EDIT: See my cleaner suggestion two messages below, this one only removes all variable)

\r wasn’t enough on my side, I had to exclude \n too

grep -vE '\r|\n'

Here’s the full line:

--env-file <(env | grep -vE '\r|\n' | grep -iE 'DEBUG|NODE_|ELECTRON_|YARN_|NPM_|CI|CIRCLE|TRAVIS|APPVEYOR_|CSC_|_TOKEN|_KEY|AWS_|STRIP|BUILD_') \

I’m not sure if that’s a good workaround though, but that did the trick for me.