Hi,
it seems backup.sh and restore.sh are not part of the DockerFile, nor the crontab is in place.

can you update your project?

best regards,

Charles.

Hi,
/backup.sh works like a charm.
but when i want to list available backups via the /restore.sh command,
an error occurs :

ERROR: Bucket 's3:' does not exist
ERROR: S3 error: 404 (NoSuchBucket): The specified bucket does not exist

according to this line https://github.com/nickbreen/docker-mysql-backup-cron/blob/master/restore.sh#L14 , BUCKET should not start with 's3://' prefix, but this is required by the backup.sh command.
When i remove from the BUCKET variable the s3:// prefix, it lists available backups successfully, but further backups fail.
best regards,
Charles.

Currently hardcoded as root and mysql, also password is $MYSQL_ENV_MYSQL_ROOT_PASSWORD, that should be specified too, with default fallbacks to the linked mysqlservice.

I forked your project in order to modify it for my purpose. Can you please add license information so that I can show it on my project?

Hi,
restoring database fails.

now sudo docker exec <docker_container_id> /backup.sh and sudo docker exec <docker_container_id> /restore.sh works, but
sudo docker exec <docker_container_id> /restore.sh <filename> returns
ERROR: S3 error: 400 (Bad Request)
i've tried with or without the 's3://' prefix, but error is the same.

best regards,

Charles.

Hi,
thanks for your work.
Can you set a version when you publish your image to the docker registry?
all versions are actually bound to the 'latest' release, which prevent to select a specific one.

best regards,

Charles.

It's easier to just use .s3cfg rather than fiddling with all the env vars.

E.g. this actually works!

  environment:
    S3_CFG: |
      [default]
      access_key = XXXX
      secret_key = XXXX
      bucket_location = ap-southeast-2
      default_mime_type = application/x-gzip
    CRON_D_BACKUP: |
      @reboot root ln -s /etc/container_environment/S3_CFG /root/.s3cfg

      @daily root (tar cz --verbose /var/www/wp-content/uploads | /usr/local/bin/s3cmd --verbose put - $$(cat /etc/container_environment/BUCKET)uploads.tar.gz) 2>&1 | logger --tag uploads

      @daily root (/usr/bin/mysqldump -uwordpress -pwordpress -hdb -B wordpress | gzip | /usr/local/bin/s3cmd --verbose put - $$(cat /etc/container_environment/BUCKET)db.tar.gz) 2>&1 | logger --tag db

There's a @reboot job that sets up the user's .s3cfg file, which all the other jobs use.

This allows for far simpler cron job spec's and permits trivial specification of arbitrary jobs and arguments.

Hi,
i've tried to override the cron expression CRON_D_BACKUP with this expression :
CRON_D_BACKUP: "* * * * * root /backup.sh | logger",
but it does not seems to work....
I don't see any reference of CRON_D_BACKUP on the project, except in the Dockerfile.
How does the cron expression is set to the system?

best regards,

Charles.

The packaged version is 1.1 and 1.6 is the current version - with the required command line parameters to specify the access key and secret