From f40878e1e75f6c57dd8df5dd134f598e8d02fe1f Mon Sep 17 00:00:00 2001 From: Thomas Waldmann Date: Wed, 13 May 2026 22:08:46 +0200 Subject: [PATCH] docs: sshfs + chroot does support different CPU architectures, fixes #6878 (cherry picked from commit 49365617c44bf8171618780014eb124de754663c) --- docs/deployment/pull-backup.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/deployment/pull-backup.rst b/docs/deployment/pull-backup.rst index 0bc352906..2a03e1c71 100644 --- a/docs/deployment/pull-backup.rst +++ b/docs/deployment/pull-backup.rst @@ -52,6 +52,14 @@ completely in every aspect from such a backup. code from the client will be executed. Therefore, you should do this only when you fully trust the client. +.. warning:: + + The SSHFS + chroot method requires that the backup server and the client + use the same CPU architecture (e.g. both x86_64), as binaries from the + client (like ``/bin/sh`` or the ``borg`` binary) are executed on the + backup server. If you have different architectures, use the :ref:`socat_method` + instead. + .. warning:: The chroot method was chosen to get the right user and group name-id @@ -205,6 +213,8 @@ Note that in this scenario the tar format is the limiting factor – it cannot restore all the advanced features that BorgBackup supports. See :ref:`borg_export-tar` for limitations. +.. _socat_method: + socat =====