1.8 Docker Backup Not Current, Won't Run, Upgrading to 1.8.2

Hi Colin

No space is indeed correct in that command. The instructions in config.env do suggest using an alpha numeric password only - and indeed link you to a password generator that generates something in the correct format.

I’d suggest changing that password to something that meets that specification to avoid ongoing issues with this.

To do so, you’d need to connect to the MySQL container, and change the password there directly, then change the password in config.env, and then rebuild the containers (with a down/up command).

Instructions for connecting to MySQL are here:

The way Docker works involves passing those secrets in to the container as environment variables, so sure we could move where the password is stored for the backup, but it would still be available in the environment variables, so I don’t think we gain anything adding that extra complexity.

Attempting any kind of encryption would be pointless as the code is open, and that would need to decrypt the password to use it, so it would be trivial for anyone to recover the password outright who had access to the container.