[BUG] Lack of AWS S3/wal-e backup leads to full disks about mattermost-docker

[eungjun-yi]

Thank you for reporiting!

Does this problem occur only if you enable the wal-e backup?

/cc @xcompass

[Psidium]

Here's the beginning of docker logs mattermost_db_1, weirdly enough, docker detects it shouldn't use wal-e 'cause it doesn't have the variables, but a little later it's already trying to backup using wal-e!

Hope this helps anyone looking into it, as always, there's a fork in my private repository.
Thanks

AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
LOG:  database system was shut down at 2016-05-04 13:23:42 UTC
LOG:  MultiXact member wraparound protections are now enabled
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
envdir: fatal: unable to switch to directory /etc/wal-e.d/env: file does not exist
LOG:  archive command failed with exit code 111
DETAIL:  The failed archive command was: envdir /etc/wal-e.d/env /usr/local/bin/wal-e wal-push pg_xlog/000000010000000000000001
LOG:  incomplete startup packet
envdir: fatal: unable to switch to directory /etc/wal-e.d/env: file does not exist
LOG:  archive command failed with exit code 111
DETAIL:  The failed archive command was: envdir /etc/wal-e.d/env /usr/local/bin/wal-e wal-push pg_xlog/000000010000000000000001
envdir: fatal: unable to switch to directory /etc/wal-e.d/env: file does not exist
LOG:  archive command failed with exit code 111
DETAIL:  The failed archive command was: envdir /etc/wal-e.d/env /usr/local/bin/wal-e wal-push pg_xlog/000000010000000000000001
WARNING:  archiving transaction log file "000000010000000000000001" failed too many times, will try again later
ERROR:  column "type" does not exist at character 40
STATEMENT:  UPDATE Preferences SET Type = $1 WHERE Type = $2
envdir: fatal: unable to switch to directory /etc/wal-e.d/env: file does not exist
LOG:  archive command failed with exit code 111
DETAIL:  The failed archive command was: envdir /etc/wal-e.d/env /usr/local/bin/wal-e wal-push pg_xlog/000000010000000000000001
envdir: fatal: unable to switch to directory /etc/wal-e.d/env: file does not exist
LOG:  archive command failed with exit code 111
DETAIL:  The failed archive command was: envdir /etc/wal-e.d/env /usr/local/bin/wal-e wal-push pg_xlog/000000010000000000000001
envdir: fatal: unable to switch to directory /etc/wal-e.d/env: file does not exist
LOG:  archive command failed with exit code 111
DETAIL:  The failed archive command was: envdir /etc/wal-e.d/env /usr/local/bin/wal-e wal-push pg_xlog/000000010000000000000001
WARNING:  archiving transaction log file "000000010000000000000001" failed too many times, will try again later
envdir: fatal: unable to switch to directory /etc/wal-e.d/env: file does not exist
LOG:  archive command failed with exit code 111
DETAIL:  The failed archive command was: envdir /etc/wal-e.d/env /usr/local/bin/wal-e wal-push pg_xlog/000000010000000000000001
envdir: fatal: unable to switch to directory /etc/wal-e.d/env: file does not exist
LOG:  archive command failed with exit code 111
DETAIL:  The failed archive command was: envdir /etc/wal-e.d/env /usr/local/bin/wal-e wal-push pg_xlog/000000010000000000000001
envdir: fatal: unable to switch to directory /etc/wal-e.d/env: file does not exist
LOG:  archive command failed with exit code 111
DETAIL:  The failed archive command was: envdir /etc/wal-e.d/env /usr/local/bin/wal-e wal-push pg_xlog/000000010000000000000001
WARNING:  archiving transaction log file "000000010000000000000001" failed too many times, will try again later
envdir: fatal: unable to switch to directory /etc/wal-e.d/env: file does not exist
LOG:  archive command failed with exit code 111
DETAIL:  The failed archive command was: envdir /etc/wal-e.d/env /usr/local/bin/wal-e awl-push pg_xlog```

[xcompass]

Thanks @Psidium. Just created a PR for this fix.