Closed lightsuner closed 5 months ago
I can confirm the issue. It gives a bit more detail in the log message:
FATA[0002] error running command: error running command: error running dump: failed to push file: failed to upload file, operation error S3: PutObject, exceeded maximum number of attempts, 3, https response error StatusCode: 0, RequestID: , HostID: , request send failed, Put "//testbucketavideitcher./db_backup_2024-04-07T13%3A16%3A54%2B03%3A00.tgz?x-id=PutObject": unsupported protocol scheme ""
How it got to that protocol scheme, I do not know. But we can step through it and find out.
That should do it. Try it out and report? Might take a few minutes to get pushed out to hub.
Hello @deitch
Thanks! The fix works! I've checked this image databack/mysql-backup:18d32f978c9281812e2615afc0bc3d096c3da1ea
I tried to use the newest version of the tool
databack/mysql-backup:51c9ce6e97a5b864bef95767c707896b95a7916b
, and received the following error:My compose.yaml file is:
At the same time, using the same config but an older version of the tool
databack/mysql-backup:latest
works well.