Skip to content

Fix S3 backup failures with RustFS and other S3-compatible storage #3339

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
Copilot wants to merge 2 commits into
base: canary
Choose a base branch
from
Draft

Fix S3 backup failures with RustFS and other S3-compatible storage #3339

Copilot wants to merge 2 commits into from
+2 −0

Conversation

Copy link
Contributor

Copilot AI commented Dec 23, 2025 •
edited
Loading

What is this PR about?

RustFS and similar S3-compatible storage backends fail during backups with "failed to seek body to start, request stream is not seekable". This occurs because rclone's default checksum verification requires stream seeking, which these backends don't support.

Added --s3-disable-checksum flag to rclone operations. This is a standard workaround for S3-compatible storage that doesn't fully implement AWS S3 checksum APIs.

Changes:

  • packages/server/src/utils/backups/utils.ts: Added flag to getS3Credentials()
  • apps/dokploy/server/api/routers/destination.ts: Added flag to connection test

Impact:
Fixes all S3 operations: volume backups/restores, database backups (Postgres, MySQL, MariaDB, MongoDB), compose operations, and web server backups.

Checklist

Before submitting this PR, please make sure that:

Issues related (if applicable)

Related to RustFS S3 backup compatibility

Screenshots (if applicable)

N/A

Original prompt

This section details on the original issue you should resolve

<issue_title>RustFS S3 Backup Failure</issue_title>
<issue_description>### To Reproduce

  1. Set up RustFS as S3-compatible storage backend
  2. Configure Dokploy S3 destination with RustFS (AWS provider)
  3. Trigger a volume backup (manual or scheduled)
  4. Observe the error in logs

Current vs. Expected behavior

S3 Backup fails with "failed to seek body to start, request stream is not seekable" .
Backup should complete successfully and upload files to the RustFS S3 bucket without errors.

Provide environment information

Dokploy Version: v0.25.11
Deployment Method: Self Hosted
OS: Ubuntu 24.04.3 LTS
RustFS Version: RUSTFS 1.0.0-alpha.76

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

Maybe, need help</issue_description>

Comments on the Issue (you are @copilot in this section)

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

@Siumauricio
Add --s3-disable-checksum flag to fix RustFS S3 backup failures
453b3d8 
Co-authored-by: Siumauricio <47042324+Siumauricio@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix S3 backup failure in RustFS Fix S3 backup failures with RustFS and other S3-compatible storage Dec 23, 2025
Copilot AI requested a review from Siumauricio December 23, 2025 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Siumauricio Siumauricio Awaiting requested review from Siumauricio Siumauricio is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

@Siumauricio Siumauricio

Copilot code review Copilot

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

RustFS S3 Backup Failure

2 participants

@Siumauricio