Docker Volume Migrator
Interactive command-line tool to copy Docker named volumes between two remote hosts over SSH – no local Docker daemon required.
Features
- 📦 Stream-based transfer – data is piped directly between hosts, never written to disk
- 🔐 SSH first – authenticate with existing SSH keys/agents
- 🎛️ Interactive wizard – guided, step-by-step prompts to pick source/target hosts & volumes
- 🐳 Minimal deps – only needs Docker &
sshon your machine; the rest happens remotely - 🪄 One command – install & run in seconds
TODO (PRs welcome)
- Direct host to host transfer with ssh keys transfer
- Tests
Installation
pip install docker-volume-migrator
or install the bleeding-edge version from GitHub:
pip install git+https://github.com/djbios/docker-volume-migrator.git
Usage
docker-volume-migrate run
The wizard will:
- Ask for the source host (SSH hostname/IP)
- List its Docker volumes and let you pick which to copy
- Ask for the target host
- Let you create new destination volumes or map to existing ones
- Show a summary and start the streaming transfer
Non-interactive / automation
All prompts have sensible defaults and can be pre-answered by setting environment variables or using CLI options (coming soon).
How it works
Under the hood, data is transferred via a TAR streaming pipeline:
ssh SRC_HOST "docker run --rm -v SRC_VOL:/from alpine tar czf - -C /from ." \
| ssh DST_HOST "docker run --rm -i -v DST_VOL:/to alpine tar xzf - -C /to"
No temporary files, no Docker daemon on your workstation.
Contributing
Pull requests welcome! Please open an issue first to discuss major changes.
# set up dev env
git clone https://github.com/djbios/docker-volume-migrator.git
cd docker-volume-migrator
uv venv # or python -m venv .venv
source .venv/bin/activate
uv pip install -e .[dev]
License
MIT © djbios
Metadata
Release files for docker-volume-migrator 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| docker_volume_migrator-0.1.0.tar.gz | 6.6 kB | Without provenance | Details for docker_volume_migrator-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| docker_volume_migrator-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for docker_volume_migrator-0.1.0-py3-none-any.whl |
Total release size: 14.2 kB
Release files / docker_volume_migrator-0.1.0.tar.gz
| Download URL | docker_volume_migrator-0.1.0.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3ed91da89d260d3e9f89ab31d5f12b5e561f2aba3eed4cc09c0bf2f8462e733a
|
|
BLAKE2b-256 checksum How to use checksums |
69b8443991e321723df0fb91a33f75f78031e05cab8763c3936c21ee3a0d97a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.27
|
Release files / docker_volume_migrator-0.1.0-py3-none-any.whl
| Download URL | docker_volume_migrator-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e32bf7be1c75e37b05d80c4afcb88f919023277fc26e1a51707c5aed2371d97
|
|
BLAKE2b-256 checksum How to use checksums |
7838cbadde07c3c4f15700b862d741679b5297ecfa10d0a466c6d81bd231fe91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.27
|
Security for docker-volume-migrator 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.