ARTIFACTORY: Nexus3 to Artifactory Migration without Docker Installation on Nexus3 Host

AuthorFullName__c
Pruthvi R B
articleNumber
000006007
FirstPublishedDate
2024-01-29T12:52:15Z
lastModifiedDate
2025-07-22

ARTIFACTORY: Nexus3 to Artifactory Migration without Docker Installation on Nexus3 Host

In this article, we will learn how to migrate from Nexus3 to Artifactory without Docker Installation on Nexus3 Host.

Following JFrog documentation, the prerequisite for utilizing the Migrator tool (script) is the installation of Docker on the Nexus Repository Manager machine to facilitate the migration process.

However, there may arise scenarios where Docker installation on the Nexus host machine is not feasible. One such example is when the Nexus Host machine operates on RHEL Red Hat Enterprise Linux Server release 6.8 (Santiago), where Docker is not officially supported.

In such instances, the following steps can be employed to enable Docker deployment and subsequently migrate the Nexus Server:

Pre-requisites : 

Launch a Separate Instance:
Deploy a distinct instance where Docker installation is supported, ensuring it resides within the same subnet as the existing Nexus box. Both the new instance and the Nexus instance should establish communication over the private IP.

Docker Installation:
Install Docker on the newly created instance, adhering to system requirements.

Configuration Setting:
Execute the following command on the newly created instance:
export SKIP_MIGRATION_FILESYSTEM_CHECK=true

This will skip checking the filesystem while initiating the migration

Migration Tool Configuration:
During the execution of the migration tool, be diligent in utilizing the private IP of the Nexus instance when providing configuration information for the Nexus Server.

Following these initial steps, further documentation can be referred to for subsequent stages of the migration process.

It is imperative to acknowledge that while these steps address the situation, it is not the recommended approach due to potential network slowness. We provide these guidelines considering the current limitations in order to navigate scenarios where Docker installation on the Nexus host is not a viable option.