{"id":48833,"date":"2024-08-29T14:10:10","date_gmt":"2024-08-29T14:10:10","guid":{"rendered":"https:\/\/accuweb.cloud\/resource\/?post_type=faq&p=48833"},"modified":"2026-02-18T06:35:17","modified_gmt":"2026-02-18T06:35:17","slug":"migrate-digitalocean-droplets","status":"publish","type":"faq","link":"https:\/\/accuweb.cloud\/resource\/articles\/migrate-digitalocean-droplets","title":{"rendered":"Migrate DigitalOcean Droplets to AccuWeb.Cloud with Docker Image"},"content":{"rendered":"

Migrating DigitalOcean Droplets to AccuWeb.Cloud with Docker Image<\/h2>\n

Migrating a DigitalOcean droplet to a Docker image and deploying it on an AccuWeb.Cloud Docker instance offers a streamlined approach to replicating your server environment across different platforms. Since direct migration of droplets is not possible due to the lack of shared backup snapshots, Docker provides a viable solution for this process.<\/p>\n

By creating a Docker image from your existing DigitalOcean setup\u2014containing the base operating system, configurations, and data files\u2014you can effectively transfer your entire environment into a Docker container.<\/p>\n

This guide will walk you through the steps to migrate your droplet<\/strong> to a Docker image and deploy it on an AccuWeb.Cloud Docker instance, ensuring a seamless transition and consistent functionality across cloud environments.<\/p>\n

Access Your DigitalOcean Droplets<\/h2>\n

Log in to your DigitalOcean account and navigate to the “Droplets”<\/strong> section from the dashboard. Here, you will see a list of all your existing droplets. This is where you will start the process of migrating your droplet to a Docker image. Select the droplet you wish to migrate to proceed with the necessary configurations and preparations.<\/p>\n

\"Select<\/a><\/p>\n

Access Your Existing DigitalOcean Droplet<\/h2>\n

SSH into your existing droplet. This article demonstrates using a droplet created with Ubuntu 22.04.<\/strong><\/p>\n

\"Access<\/a><\/p>\n

Update the System<\/h3>\n

Update the package list and upgrade installed packages with<\/p>\n

<\/div>\n
\r\napt-get update && apt-get upgrade -y<\/code><\/pre>\n
<\/div>\n
\"Update<\/a><\/p>\n
Install Apache and PHP<\/h3>\n
Install Apache and PHP with<\/p>\n
<\/div>\n
\r\napt-get install -y apache2 php<\/code><\/pre>\n
<\/div>\n
For this article, we will also create a test PHP file.<\/p>\n
\"Create<\/a><\/p>\n
Verify Apache is Running<\/h3>\n
Check if Apache is running by executing<\/p>\n
<\/div>\n
\r\nsystemctl status apache2<\/code><\/pre>\n
<\/div>\n
\"Verify<\/a><\/p>\n
Add Content\/Files<\/h3>\n
Create a sample PHP file with<\/p>\n
<\/div>\n
\r\necho \"<?php phpinfo(); ?>\" > \/var\/www\/html\/info.php<\/code><\/pre>\n
<\/div>\n
\"Add<\/a><\/p>\n
Set Correct Permissions for Apache<\/h3>\n
Ensure Apache has the correct permissions for the files by running<\/p>\n
<\/div>\n
\r\nchown www-data:www-data \/var\/www\/html\/info.php<\/code><\/pre>\n
<\/div>\n
\"Set<\/a><\/p>\n
Verify Access via Web Browser<\/h3>\n
Confirm you can access the file by navigating to http:\/\/<your-droplet-ip>\/info.php<\/strong> in a web browser.<\/p>\n
Default index file<\/h3>\n
\"Verify<\/a><\/p>\n
Info.php<\/h3>\n
\"Info.Php\"<\/a><\/p>\n
Create Docker Image<\/h2>\n
Before we create a Docker image, we need to ensure that Docker is installed and running on your droplet. Docker is a platform that automates the deployment of applications inside lightweight, portable containers, making it an essential tool for modern development environments.<\/p>\n
Install Docker on your droplet with<\/p>\n
<\/div>\n
\r\napt-get install -y docker.io<\/code><\/pre>\n
<\/div>\n
Enable Docker to start automatically on boot<\/p>\n
<\/div>\n
\r\nsystemctl enable docker<\/code><\/pre>\n
<\/div>\n
Start the Docker service with<\/p>\n
<\/div>\n
\r\nsystemctl start docker<\/code><\/pre>\n
<\/div>\n
\"Create<\/a><\/p>\n
Prepare Dockerfile<\/h2>\n
To create a Docker image that includes Apache and PHP, follow these steps to set up a Dockerfile. This file will install the necessary packages and copy your sample files into the container.<\/p>\n
<\/div>\n
Note:<\/strong> For this setup, the Dockerfile was created in the \/root<\/strong> directory. Additionally, a folder named html was created within \/root [same directory],<\/strong> into which the required files from \/var\/www\/html\/<\/strong> were copied. This ensures that all necessary files are within the Docker build context, as Docker requires all files included in the image to be located in the build context directory.<\/div>\n
<\/div>\n
Create a Dockerfile<\/strong> with the following code:<\/p>\n
<\/div>\n
\r\n# Use Ubuntu 22.04 as the base image\r\nFROM ubuntu:22.04\r\n# Set environment variables to avoid interactive prompts\r\nENV DEBIAN_FRONTEND=noninteractive\r\n# Install Apache and PHP\r\nRUN apt-get update && apt-get install -y \\\r\napache2 \\\r\nphp \\\r\n&& apt-get clean \\\r\n&& rm -rf \/var\/lib\/apt\/lists\/*\r\n# Copy the entire \/html directory into the container\r\nCOPY html \/var\/www\/html\r\n# Expose port 80 for web traffic\r\nEXPOSE 80\r\n# Start Apache in the foreground\r\nCMD [\"apachectl\", \"-D\", \"FOREGROUND\"]<\/code><\/pre>\n
<\/div>\n
\"Create<\/a><\/p>\n
Build Docker Image<\/h2>\n
Build the Docker image using the following command<\/p>\n
<\/div>\n
\r\ndocker build -t marvingdocker\/full-system-image .<\/code><\/pre>\n
<\/div>\n
Here’s a breakdown of each parameter:<\/strong><\/p>\n
docker build<\/strong>\u00a0This is the Docker command used to create a new image from a Dockerfile.<\/p>\n
-t marvingdocker\/full-system-image<\/strong>\u00a0The -t flag tags the image with a name and optionally a tag. In this case, marvingdocker\/full-system-image<\/strong> is the name assigned to the image. You can think of it as a label for the image, where marvingdocker<\/strong> is the username or organization and full-system-image<\/strong> is the name of the image. You can also append a tag (e.g., :v1<\/strong>) to specify a version.<\/p>\n
. <\/strong>The period represents the build context, which is the directory containing the Dockerfile and any files it needs. In this case, . refers to the current directory. Docker will use this context to locate the Dockerfile and any other files specified in it (like info.php<\/strong> in this example).<\/p>\n
\"Build<\/a><\/p>\n
<\/div>\n
Note:<\/strong> Docker’s build context limitation requires that all files to be included in the image must be within the directory from which the docker build command is run. Docker cannot access files outside this context for security and efficiency reasons. Therefore, ensure all necessary files and directories are copied into the build context before building the image.<\/div>\n
<\/div>\n
\"docker<\/a><\/p>\n
Verify Docker Image<\/h2>\n
To confirm that your Docker image was created successfully, use the following command to list all available images on your system:<\/p>\n
<\/div>\n
\r\ndocker images<\/code><\/pre>\n
<\/div>\n
This command will display a list of Docker images, including the repository name, tag, and image ID. Verify that marvingdocker\/full-system-image<\/strong> appears in the list with the correct tag.<\/p>\n
\"Verify<\/a><\/p>\n
Push Docker Image to Docker Hub<\/h3>\n
Log in to Docker Hub<\/h3>\n
To push your Docker image to Docker Hub, you first need to log in to your Docker Hub account. Use the following command to authenticate:<\/p>\n
<\/div>\n
\r\ndocker login<\/code><\/pre>\n
<\/div>\n
You will be prompted to enter your Docker Hub username and password. Once authenticated, you will be able to push images to your Docker Hub repositories.<\/p>\n
\"LogIn<\/a><\/p>\n
Tag and Push the Docker Image<\/h3>\n
It’s recommended to tag your Docker image for clarity, especially if you plan to push it to Docker Hub:<\/p>\n
<\/div>\n
\r\ndocker tag marvingdocker\/full-system-image marvingdocker\/full-system-image:v1.0<\/code><\/pre>\n
<\/div>\n
This tags your image with a version tag (v1.0), making it easier to manage and identify different versions.<\/p>\n
<\/div>\n
Note:<\/strong> Tagging is optional, and if you do not specify a tag, Docker uses the default latest tag.<\/div>\n
<\/div>\n
Once tagged, push the Docker image to Docker Hub<\/strong><\/p>\n
<\/div>\n
\r\ndocker push marvingdocker\/full-system-image<\/code><\/pre>\n
<\/div>\n
\"Push<\/a><\/p>\n
This will upload the image to your Docker Hub repository, making it accessible from anywhere.<\/strong><\/p>\n
Verify Push<\/h3>\n
You can log in to your Docker Hub account and verify that the pushed image appears in your repository. Simply navigate to the repository section of your Docker Hub account, and you should see the image listed there with the tags you specified.<\/p>\n
\"Verify<\/a><\/p>\n
We have successfully pushed the Docker image, created from a DigitalOcean droplet, to Docker Hub. We will now import this image into the Docker template section of the AccuWeb.Cloud dashboard <\/a>\u00a0and use it to create a new instance. This will enable us to deploy and manage our application efficiently within the AccuWeb.Cloud environment.<\/p>\n
Access the AccuWeb.Cloud Dashboard<\/h2>\n
Step 1.<\/strong> Log in<\/strong> to your AccuWeb.Cloud account.<\/p>\n
Step 2.<\/strong> Select the New Environment<\/strong> option from the menu on the left side of the screen.<\/p>\n
\"New<\/a><\/p>\n
Add Docker Image to AccuWeb.Cloud<\/h2>\n
Navigate to the Custom Tab<\/h3>\n
Go to the Custom<\/strong> tab in the Topology window and select the Application Servers<\/strong> option.<\/p>\n
\"Add<\/a><\/p>\n
Add New Image<\/h3>\n
In the Application Servers window, select Custom<\/strong> and click on the Add New Image<\/strong> option.<\/p>\n
\"Custom<\/a><\/p>\n
Enter Image Details<\/h3>\n
In the Add New Image<\/strong> window, provide the following information:<\/p>\n