V1.10 Migrator

V1.10 Migrator is a historical Docker utility that pre-calculates SHA256 content-addressable checksums for existing image layers, letting Docker Engine 1.9…

  • Infrastructure
  • Tools & Utilities
V1.10 Migrator is a historical Docker utility that pre-calculates SHA256 content-addressable checksums for existing image layers, letting Docker Engine 1.9 hosts upgrade to 1.10 without the slow automatic migration that blocks the daemon at first startup.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

26/100 Low

Maintained
0GitHub repository is archived
Popular
2824 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
79no serious findings, 1 minor, tests

Based on 4 of 5 factors.

GitHub stars
24
Open issues
12
Last commit
2016-02-19
Latest release
1.0.2
License
Apache-2.0
Activity
stale

Checked 15 days ago - source: GitHub (docker-archive/v1.10-migrator)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Usage Run the container while your old Docker daemon is still active. Key flags: --graph (Docker root dir, default /var/lib/docker) and --storage-driver (driver to migrate, default auto). source
  • Running the migration Run the image as a one-off container while your existing Docker 1.9 daemon is still running. It pre-computes the SHA-256 checksums for your image layers so the daemon does not have to do it (and block requests) during first startup after you upgrade to 1.10. Use --graph to point at the Docker root directory (default /var/lib/docker) and --storage-driver to force a storage driver instead of auto. source
  • Running the migrator Run v1.10-migrator while your existing (pre-1.10) Docker daemon is still running, before starting Docker 1.10, so it pre-calculates the layer checksums and the new daemon starts without a slow, blocking migration. Point it at the Docker root with --graph (default /var/lib/docker) and choose the storage driver with --storage-driver (default auto). source
  • Pre-computing checksums before upgrade Run v1.10-migrator while the old Docker Engine 1.9 daemon is still active (e.g. v1.10-migrator --graph /var/lib/docker) to pre-compute SHA256 checksums for all image layers, then start Docker Engine 1.10 to skip the slow automatic migration at daemon startup. source
  • Legacy status This is a one-time migration tool for upgrading from Docker Engine 1.9 to 1.10. The repository has been archived by Docker (docker-archive) and the tool is no longer actively maintained. source
  • Avoid the slow daemon-start migration Start the migrator while your Docker 1.9 daemon is still running (bind its data dir with --graph /var/lib/docker) to pre-compute the new content-addressable checksums; once it finishes, upgrade the daemon to 1.10 to skip the migration that would otherwise run and block startup. source

Fetched 9 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What Docker 1.11 pull problem has been reported after running the Docker v1.10 migrator?

Pulling the migrated images can fail with an unsupported digest algorithm error.

Answers sourced from forums.docker.com

Community

Collected 48 days ago - public community threads