{"id":35751,"date":"2026-01-12T00:35:07","date_gmt":"2026-01-11T17:35:07","guid":{"rendered":"https:\/\/dps.media\/xay-dung-he-thong-docker-custom-backup-deep-space-chi-voi-next-js-dockerode\/"},"modified":"2026-01-12T00:35:07","modified_gmt":"2026-01-11T17:35:07","slug":"build-docker-custom-backup-system-deep-space-only-next-js-dockerode","status":"publish","type":"post","link":"https:\/\/dps.media\/en\/build-docker-custom-backup-system-deep-space-only-next-js-dockerode\/","title":{"rendered":"Building a Custom Docker Backup System \u201cDeep Space\u201d Using Only Next.js & Dockerode"},"content":{"rendered":"

Introduction: The Nightmare Called \u201cManual Backup\u201d<\/h2>\n

If you are a programmer, a System Admin or simply a science lover operating personal VPS, you must have experienced the chilling sensation when you accidentally typed the command rm -rf<\/code> in the wrong directory, or on a fine day the Database Container suddenly dies without apparent reason.<\/p>\n

Managing backups for Docker Container on VPS usually revolves around the following solutions:<\/p>\n

    \n
  1. Cronjob + Shell Script:<\/strong> This is the most common way. You write a script backup.sh<\/code>, compress the volume directory and push it to the Cloud. It sounds simple but when the number of containers reaches dozens, managing this pile of scripts is a real ordeal. Not to mention that restoring is extremely manual and prone to errors.<\/li>\n
  2. Using Existing Tools (Portainer, Yacht\u2026):<\/strong> These tools are great for managing Containers, but backup features are often quite basic, or require the Business version (paid) to have scheduling or advanced automatic backup features.<\/li>\n
  3. No backup at all:<\/strong> \u201cIt probably won't happen to me\u201d \u2013 and this is often the beginning of sad data loss stories.<\/li>\n<\/ol>\n

    Because of those pains, I decided to build with my own hands Docker Guard<\/strong> \u2013 A professional Backup & Restore system, with a sci-fi movie-like interface, and most importantly: It completely solves the safe backup problem.<\/strong><\/p>\n

    \"Docker<\/p>\n

    System Architecture & Tech Stack \u201cDeep Space\u201d<\/h2>\n

    Instead of writing a dry Desktop or CLI application, I chose to build Docker Guard as a modern Web Application. This allows me to access and manage backups from anywhere, on phone or laptop, as long as there's a browser.<\/p>\n

    \"Docker<\/p>\n

    Why Next.js?<\/h3>\n

    Many of you might wonder: \u201cWhy use Next.js (Node.js\/React) for System management instead of Python or Go?\u201d.<\/p>\n

    The answer lies in flexibility and development speed. With Next.js 14 (App Router)<\/strong>, I can:<\/p>\n

      \n
    • Backend (Server Actions):<\/strong> Write Node.js code that runs directly on the Server to communicate with Docker Daemon, handle file system, zip compression\u2026 without needing to set up a separate Express\/NestJS server.<\/li>\n
    • Frontend (React Server Components):<\/strong> Render interface extremely fast, good SEO (even though internal tools don't need much SEO, but fast loading is satisfying).<\/li>\n
    • Real-time UI:<\/strong> Easily integrate Streaming UI to display running backup logs in real-time.<\/li>\n<\/ul>\n

      \"Docker<\/p>\n

      In addition, the interface is meticulously crafted with Tailwind CSS<\/strong> and Framer Motion<\/strong>. I drew inspiration from Cyberpunk\/Sci-fi interfaces with a dark color scheme (Deep Space), Glassmorphism effects (frosted glass) and Neon lighting. Server management doesn't have to be boring with black and white screens, it has to be \u201ccool\u201d to be motivated to work!<\/p>\n

      3 Money-Making Features of Docker Guard<\/h2>\n

      1. Smart Backup: Not Just Copying Data<\/h3>\n

      Most common backup scripts only perform tar<\/code> (compression) of volume directories. But what if you lose the entire VPS? You have the data, but you forget what docker run<\/code> command you used, with which environment variables, which ports mapped externally?<\/p>\n

      Docker Guard solves this with the \u201cSmart Backup\u201d mechanism:<\/strong><\/p>\n

        \n
      1. Inspect Container:<\/strong> The tool will read the entire current configuration of the container (Image tag, Env vars, Ports, Network settings, Cmd\u2026).<\/li>\n
      2. Serialize Config:<\/strong> Save that configuration to a file config.json<\/code>.<\/li>\n
      3. Compress Volumes:<\/strong> Compress all data from Volumes mounted into the container.<\/li>\n
      4. Package:<\/strong> Package everything into a single .zip<\/code> file.<\/li>\n<\/ol>\n

        \"Smart<\/p>\n

        Thanks to this, Docker Guard's backup file is like a \u201cresurrection pill\u201d. You take this zip file to a brand new VPS, click Restore, and boom! Your container comes back to life exactly as before, with every environment variable, every image version intact.<\/p>\n

        2. Restore to New Container: Clone for Safe Testing<\/h3>\n

        This is the feature I'm most proud of and use the most. In a Production environment, restoring over a running container is an extremely high risk. What if the backup file is corrupted? What if the new version is incompatible with old data?<\/p>\n

        Docker Guard allows you to perform \u201cRestore to New Container\u201d<\/strong>. Instead of overwriting, it will:<\/p>\n

          \n
        • Create a new container with an example name: my-app_restored_20231025<\/code>.<\/li>\n
        • Map a random port (or one you choose) to avoid port conflicts with the main app (Live App).<\/li>\n
        • Data is extracted into a separate folder.<\/li>\n<\/ul>\n

          \"Restore<\/p>\n

          At this point, you have 2 containers running in parallel: the Live version and the Restore version. You can enter the Restore version to check, test if the data is okay, if the code runs stably. When everything is 100% certain, then you switch traffic over or replace the old one. This is the process Zero Downtime Recovery<\/strong> that large systems often use.<\/p>\n

          3. Smart Queue<\/h3>\n

          Backup is a resource-intensive task (CPU for compression, Disk I\/O for reading\/writing). If you schedule 10 containers to backup at the same time at midnight, your VPS will likely hang (High Load).<\/p>\n

          Docker Guard integrates a smart queue (Queue) by default. Even if you click \u201cBackup All\u201d, it will process each container one by one (or 2-3 depending on Worker configuration). This container finishes before the next, ensuring the VPS always runs smoothly, never overloaded.<\/p>\n

          DIY Guide: Build Your Own Backup Tool<\/h2>\n

          If you're interested and want to code a similar tool yourself, the key lies in communicating with the Docker Daemon.<\/p>\n

          Step 1: Mount Docker Socket<\/h3>\n

          Docker Daemon listens for commands via a Unix Socket at \/var\/run\/docker.sock<\/code>. To allow our Node.js app to control Docker, we need to mount this file into the app's container.<\/p>\n

          # docker-compose.yml\nservices:\n  my-backup-app:\n    image: node:18-alpine\n    volumes:\n      - \/var\/run\/docker.sock:\/var\/run\/docker.sock # The key is here\n<\/code><\/pre>\n
          Step 2: Use Dockerode Library<\/h3>\n
          Instead of calling shell commands docker exec...<\/code> (very crude and hard to parse results), we use the library dockerode<\/code>.<\/p>\n
          import Docker from 'dockerode';\n\n\/\/ Connect via mounted socket\nconst docker = new Docker({ socketPath: '\/var\/run\/docker.sock' });\n\nasync function backupContainer(containerId) {\n    const container = docker.getContainer(containerId);\n    \n    \/\/ 1. Get configuration info\n    const data = await container.inspect();\n    const env = data.Config.Env;\n    const image = data.Config.Image;\n    \n    console.log(`Backing up container: ${data.Name} - Image: ${image}`);\n    \n    \/\/ 2. Handle backup volume (File compression logic)...\n    \/\/ ... code handling archiver (zip) ...\n}\n<\/code><\/pre>\n
          Step 3: Handle Stream (Data Stream)<\/h3>\n
          For large data (several GB), absolutely do not read everything into RAM. Use Node.js Stream to \u201cpump\u201d data from Docker exec output directly into the compressed file.<\/p>\n
          \/\/ Example pipeline illustration\nimport { pipeline } from 'stream\/promises';\nimport fs from 'fs';\nimport zlib from 'zlib';\n\nawait pipeline(\n    dockerStream, \/\/ Stream from container\n    zlib.createGzip(), \/\/ Gzip compression\n    fs.createWriteStream('.\/backup.tar.gz') \/\/ Write to disk\n);\n<\/code><\/pre>\n
          Summary<\/h2>\n
          Building internal tools (Internal Tools) like Docker Guard<\/strong> not only makes operations work lighter and safer but is also a great opportunity for us to learn deeper about the system. Understanding Docker Socket, Streams, System Architecture will make you a more well-rounded software engineer.<\/p>\n
          If you're also struggling with backups, try building a small tool for yourself. The feeling of watching progress bars run smoothly and green \u201cBackup Success\u201d notifications is really addictive!<\/p>\n
          See you in the next technical sharing articles about DevOps and System Administration!<\/em><\/p>\n