You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it would be helpful to gzip compress volume backs when used via https://docs.dokploy.com/docs/core/volume-backups or have an option to do so. Especially for use-cases like sqlite where the backup sizes will greatly reduce storage.
Current vs. Expected behavior
volume creates only create a tar file - application/x-tar - but a .tar.gz would better utilise storage space on s3
Provide environment information
Version: v0.26.6
Ubuntu
Which area(s) are affected? (Select all that apply)
Application, Docker
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?
No
Reacted by Yarkov Aleksey, Nick Pappas, denogio, inkfish and Anxo
I've opened PR #5206 with gzip compression for volume backups (tar cvf → tar czf, .tar → .tar.gz). Tested locally with MinIO as S3 destination — backups compress ~15:1 for text/JSON/SQLite data.
I also explored zstd and shared the findings in the discussion #2991 — including the trade-offs and a proposed path forward if the team wants to go beyond gzip.
Activity
denogio commentedon May 7, 2026
Surprised it is not compressed by default.
anxo-outeiral commentedon Jun 11, 2026
Totally agree with this.
anxo-outeiral commentedon Aug 28, 2026
I've opened PR #5206 with gzip compression for volume backups (
tar cvf→tar czf,.tar→.tar.gz). Tested locally with MinIO as S3 destination — backups compress ~15:1 for text/JSON/SQLite data.I also explored zstd and shared the findings in the discussion #2991 — including the trade-offs and a proposed path forward if the team wants to go beyond gzip.
feat(volume-backups): add gzip compression to volume backups