How do I run n8n on Docker? 

Key highlights 

• Understand n8n as a powerful open-source automation tool designed to link APIs, services, and applications seamlessly. 

• Learn how Docker provides an isolated, reliable environment specifically tailored for running n8n securely. 

• Explore the flexibility of launching n8n via a single Docker command or by utilizing Docker Compose for advanced setups. 

• Know how utilizing Docker volumes ensures your workflows and important credentials remain intact even after container reboots. 

• Uncover how self-hosting n8n on a VPS grants you absolute control over your automation ecosystem. 

If your goal is to automate tasks without being tethered to third-party providers, n8n stands out as an exceptional option. It empowers you with complete authority over your integrations, whether you are syncing databases, calling APIs, or crafting highly specialized workflows. 

Deploying n8n via Docker is arguably the simplest way to begin. Docker conveniently bundles all necessary n8n dependencies into a single container, eliminating the headache of manual system configurations. This results in a fast, tidy, and reproducible setup process across any machine. 

Throughout this comprehensive guide, you will discover how to install n8n utilizing Docker, configure it effectively with Docker Compose, and even self-host the platform on a Bluehost VPS. By the conclusion, you will possess a fully functional n8n Docker environment primed for your automation tasks. 

Before we dive into the installation process, let’s explore what makes this platform so powerful. 

What is n8n and why run it on Docker? 

As an open-source workflow automation platform, n8n enables you to bridge the gap between distinct services and tools without needing to write intricate code. 

With n8n, you can easily: 

• Streamline and automate mundane, repetitive tasks 

• Link databases and various APIs together 

• Construct sophisticated event-triggered workflows 

• Transition away from costly tools like Zapier in favor of a self-hosted alternative 

Benefits of running n8n with Docker 

Operating n8n within a Docker container heavily streamlines the deployment and increases reliability. 

Here is why it remains the preferred choice for many developers: 

• Isolation: Docker neatly separates n8n from your underlying OS, avoiding dependency conflicts. 

• Simple installation: Firing up n8n takes just minutes and a single terminal command. 

• Consistent environment: Docker guarantees your setup will perform identically regardless of the host system. 

• Easy updates: Upgrading n8n is as simple as fetching the latest container image. 

Now that we understand the benefits, let’s review the requirements you need to meet before starting. 

Prerequisites for running n8n on Docker 

Before launching n8n on Docker, ensure your operating system and utilities are properly prepared. This proactive step prevents unexpected setup hurdles and guarantees stable performance. 

1. System requirements 

While n8n is relatively lightweight for basic tasks, automation demands can spike rapidly if you handle large payloads or execute frequent triggers. It’s wise to allocate extra resources. 

• OS: Windows, macOS, or Linux 

• RAM: A minimum of 2 GB for testing; 4 GB or higher is strongly suggested for continuous operation 

• CPU: At least 1–2 vCPUs, scaling upwards for heavy concurrency 

• Access: Local terminal access or SSH capabilities for remote servers 

2. Required tools 

To execute n8n via Docker, Docker Engine is mandatory. For an optimal, long-term deployment, Docker Compose (which is now natively integrated as docker compose) is also necessary. 

• Docker Engine 

• Docker Compose 

• An active internet connection to download the required container images 

3. Verify Docker installation 

Prior to installing n8n, verify that Docker is operational and that Compose functions correctly on your machine. 

• Execute: docker –version 

• Execute: docker compose version 

If these commands return errors, resolve your Docker installation first. Linux users might need to append their user to the Docker group or utilize sudo. For guidance on server access, review standard Linux permissions and sudo practices. 

With the prerequisites cleared, let’s jump into the fastest way to get your automation environment running. 

How do I run n8n on Docker: quick method (single command) 

This approach is perfect for local development, swift testing, or temporary setups. It serves as the fastest method to ensure your volumes and ports are functioning before transitioning to a comprehensive n8n Docker setup via Compose. 

Step 1: Install Docker 

Docker must be present on your host machine before running n8n. 

For Linux (Ubuntu): 

sudo apt update 
sudo apt install docker.io -y  

Next, initiate the Docker service: 

sudo systemctl start docker 
sudo systemctl enable docker  

For macOS or Windows: 

Grab Docker Desktop straight from Docker’s official site and install it. 

Once finished, launch Docker Desktop and confirm the engine is running. 

Validate your Docker installation: 

docker --version 
docker compose version  

Seeing the respective version numbers indicates Docker is ready. 

Step 2: Create a Docker volume 

Establishing a named Docker volume is crucial so n8n can securely save encryption keys, workflows, and credentials independently of the container’s temporary filesystem. Skipping this step means risking total data loss if the container is deleted. 

Execute this command to instantiate the volume: 

docker volume create n8n_data  

This ensures your configurations are protected even when the container halts. 

Step 3: Run the n8n container 

You can leverage a solitary docker run command to get n8n online rapidly. This represents the simplest technique to run n8n on Docker for a single-node setup. 

Basic example command for local testing: 

docker run -it --rm --name n8n \ 
-p 5678:5678 \ 
-v n8n_data:/home/node/.n8n \ 
docker.n8n.io/n8nio/n8n  

What this command does: 

This snippet pulls the latest n8n image and executes it locally using Docker. 

Option	What it means
-it	Engages interactive mode, allowing you to view real-time logs in your terminal
–name n8n	Assigns a memorable name to the container for straightforward management
-p 5678:5678	Bridges the container’s port to your local machine at http://localhost:5678
-v n8n_data:/home/node/.n8n	Persists your settings, credentials, and workflows to prevent data deletion
–rm	Automatically deletes the container upon stopping. Excellent for quick tests, but avoid in production
docker.n8n.io/n8nio/n8n	Points to the official n8n Docker image required to run the platform

Step 4: Access the n8n interface 

Once the container is active, n8n is accessible via your web browser. 

• If deploying on a local computer: 
  Navigate to http://localhost:5678 

• If deploying on a server or VPS: 
  Navigate to http://YOUR_SERVER_IP:5678 

This action launches the n8n visual editor, allowing you to begin crafting your automations immediately. 

If the page does not load 

• Confirm that the Docker container is actively running without errors 

• Ensure port 5678 is fully open and unrestricted 

• If on a VPS, verify that your firewall rules permit inbound traffic on this specific port 

While the single command is great for a quick test, a more robust setup is highly advised for long-term usage. 

How do I run n8n on Docker with Docker Compose (recommended)? 

For those intending to self host n8n for the foreseeable future, Docker Compose remains the superior choice. It consolidates all configurations within a single YAML file, streamlines upgrades, and easily accommodates production-grade additions like external databases, restart policies, and reverse proxies. 

• Centralized configuration: Keep volumes, ports, and environment variables neatly organized in one document 

• Easier container management: Stop, start, and reboot your services with minimal keystrokes 

• Supports production deployments: Effortlessly integrate backups, a proxy server, or PostgreSQL 

If you prefer an intuitive, visual approach to container management, setting up a tool like Portainer is also highly recommended. 

Let’s break down exactly how to set up this recommended configuration. 

Step-by-step: Deploy n8n with Docker Compose 

Opting for Docker Compose yields an environment that is significantly easier to maintain. Rather than relying on a cumbersome docker run command for every launch, your settings are permanently saved. 

This translates to a cleaner workspace and drastically simplified future updates. 

Why Docker Compose is better? 

Docker Compose empowers you to control your n8n architecture with minimal friction. 

Benefits of Docker Compose: 

• Easier container management 
  You can manage service lifecycles (start, stop, restart) using concise commands. 

• Centralized configuration 
  Crucial elements like environment variables, volumes, and ports live inside a single docker-compose.yml file. 

• Better suited for production environments 
  It scales beautifully as your infrastructure demands grow, making maintenance a breeze. 

Once again, let’s look at the precise steps to get this deployed. 

Step-by-step: Deploy n8n with Docker Compose 

Running n8n on Docker provides a stable and isolated environment for your automation workflows. By using Docker Compose, you can easily manage your setup and dependencies through a single configuration file, making the deployment process quick and efficient.

Step 1: Install Docker and Docker Compose 

Prior to diving in, verify Docker is active on your machine or server. As of Docker v20.10.0, the Compose plugin is bundled natively, meaning a separate installation is no longer required. 

If you operate within a highly customized server space, you might need to manually install Docker via your OS package manager. 

For those on Windows or macOS, deploying Docker Desktop will furnish both Docker Engine and Docker Compose automatically. 

Post-installation, confirm the setup by typing: 

docker -v  

The appearance of a version number confirms Docker is fully operational. 

Now let’s move on to preparing your workspace. 

Step 2: Create a project directory 

Proceed by generating a unique folder strictly for your n8n configuration: 

mkdir n8n-docker 
cd n8n-docker  

This directory will act as the home for your Compose file and its associated data. 

Consolidating these files in a single folder simplifies future migrations, updates, and general management. 

Step 3: Create a docker-compose.yml file 

Within your newly created n8n-docker directory, generate a file titled: 

docker-compose.yml  

This document will hold the complete blueprint Docker needs to execute n8n. 

Populate it with the following YAML structure: 

version: "3.8" 
services: 
  n8n: 
    image: docker.n8n.io/n8nio/n8n 
    container_name: n8n 
    ports: 
      - "5678:5678" 
    volumes: 
      - n8n_data:/home/node/.n8n 
    environment: 
      - N8N_HOST=localhost 
      - N8N_PORT=5678 
      - N8N_PROTOCOL=http 
volumes: 
  n8n_data:  

Note: This setup is intended for local development and testing only. Do NOT expose port 5678 directly to the public internet in production environments.  For live deployments, always use a reverse proxy, HTTPS, and proper access controls. 

Understanding this configuration 

Setting	What it means
image	Instructs Docker to pull the authorized n8n image
container_name	Tags the container with a readable name for streamlined commands
ports	Forwards container port 5678 to your local environment for browser access
volumes	Guarantees persistent storage, keeping your configurations and automations secure
environment	Dictates core n8n parameters, including protocol, listening port, and host

Essentially, this configuration file replaces unwieldy command-line arguments and keeps your setup structured. 

Step 4: Start the container 

Trigger the deployment with: 

docker compose up -d  

This command launches n8n relying exclusively on the parameters defined in your docker-compose.yml. 

What -d means 

The -d argument stands for “detached mode.” 

Practically, this means: 

• Docker processes the container silently in the background 

• Your command-line interface immediately becomes available for new inputs 

• n8n will operate continuously until manually halted 

In short, it fires up n8n and allows it to hum along quietly behind the scenes. 

Step 5: Check container status 

To verify that n8n deployed successfully, utilize: 

docker compose ps  

The output will reveal: 

• The container’s designated name 

• Its active status (whether stopped or running) 

• The specific port mappings 

If the output lists the container as running, your n8n instance is healthy. 

Step 6: Access the n8n interface 

Point your preferred web browser to: 

• Local setup: http://localhost:5678 

• Server/VPS: http://YOUR_SERVER_IP:5678 

This action will reveal the main n8n dashboard. 

Should you face connection issues: 

• Double-check any server firewall restrictions 

• Confirm the container hasn’t crashed or stopped 

• Validate that port 5678 is accepting incoming traffic 

Let’s take a moment to review what we’ve accomplished. 

Summary 

Through this walkthrough, you have successfully: 

• Installed and validated your Docker environment 

• Prepared an isolated project folder 

• Structured your infrastructure via a single YAML file 

• Launched n8n in detached mode 

• Verified the container’s operational status 

• Logged into the n8n interface successfully 

This Compose-driven strategy is considerably more durable and organized than a basic docker run setup. It is built to scale and represents the gold standard for production-level deployments. 

To ensure your platform communicates properly with other services, you must adjust some key settings. 

Configure environment variables for n8n 

Environment variables dictate crucial behaviors for n8n, such as database connectivity, webhook URL structures, and routing. Perfecting these configurations marks the transition from a casual local test to a formidable n8n Docker setup. 

Important variables 

At a bare minimum, you must configure your host and webhook variables when placing n8n behind a domain name or proxy. Defining your local time zone is also essential for accurate scheduling, as are database credentials if you upgrade to PostgreSQL. 

• N8N_HOST: The target hostname for your instance (e.g., n8n.yourdomain.com) 

• N8N_PORT: The container’s internal listening port (defaults to 5678) 

• N8N_PROTOCOL: Define as http or https (typically https when paired with a proxy) 

• WEBHOOK_URL: The external-facing URL for receiving webhooks (absolute necessity for production) 

• GENERIC_TIMEZONE: Your preferred system time zone (e.g., America/New_York) 

• Database settings: Configuration required when bridging to PostgreSQL for enhanced durability 

A standard environment snippet for a domain-hosted setup looks like this: 

• Example:  

• – N8N_HOST=n8n.yourdomain.com 

• – N8N_PROTOCOL=https 

• – WEBHOOK_URL=https://n8n.yourdomain.com 

• – GENERIC_TIMEZONE=UTC 

Keep these two vital operational guidelines in mind: 

• If your WEBHOOK_URL is misconfigured, external APIs will fail to reach your n8n instance, breaking integrations. 

• Whenever you modify your environment variables, apply them by running: docker compose up -d. 

For more advanced production tweaks, such as implementing strict authentication, consult basic server security practices and the official n8n configuration documentation. 

If you prefer a hosted environment instead of a local machine, using a virtual private server is an excellent choice. 

How to run n8n on Docker using Bluehost VPS? 

Hosting n8n on a Virtual Private Server (VPS) furnishes you with uncompromised control over scalability, storage, and networking. Fortunately, with Bluehost, you can bypass the tedious manual Docker configurations entirely. 

Use Bluehost one-click n8n installation (recommended) 

Bluehost offers an intuitive one-click n8n installation template. This powerful feature circumvents the need to manually install dependencies, adjust containers, or wrangle Docker commands. 

Why use this method: 

• Eliminates manual Docker scaffolding 

• Delivers a perfectly tuned, preconfigured n8n environment 

• Provides a significantly faster, beginner-friendly deployment 

• Minimizes the risk of setup errors and saves precious time 

Once the automated deployment finishes, you can log directly into your n8n dashboard without sweating over technical details. 

Post-installation access URL: 

http://YOUR_SERVER_IP:5678 

For those who want granular control over their server, here is the hands-on approach. 

Manual method (advanced users) 

If you mandate maximum customization or simply enjoy having full control over your infrastructure, a manual installation on a VPS is totally viable. 

1. Connect to your Bluehost VPS 

Begin by establishing an SSH connection to your server: 

ssh username@YOUR_SERVER_IP  

You will require: 

• Your Server IP address 

• Your administrative Username 

• Your Password or a matching SSH key 

2. Install Docker on the VPS 

Fetch and install Docker utilizing your operating system’s package manager. 

• For Ubuntu: Download the Docker packages and initialize the service 

• For AlmaLinux/CentOS: Inject the Docker repository and enable the application 

Verify success with: 

docker -v  

3. Create a Docker volume 

docker volume create n8n_data  

This critical step safeguards your: 

• Active workflows 

• Authentication credentials 

• Platform settings 

It ensures permanent storage that survives container shutdowns. 

4. Run the n8n container 

docker run -d --name n8n \ 
-p 5678:5678 \ 
-v n8n_data:/home/node/.n8n \ 
--restart unless-stopped \ 
docker.n8n.io/n8nio/n8n  

This command launches n8n securely in the background, instructing it to automatically restart if the server reboots. 

5. Access the n8n dashboard 

Navigate to your browser and input: 

http://YOUR_SERVER_IP:5678  

If you encounter a loading error: 

• Confirm Docker hasn’t halted the container 

• Check that port 5678 is successfully mapped 

• Audit your VPS firewall policies 

6. Optional: Connect a domain and enable HTTPS 

For rigorous production deployments: 

• Link a domain name to your server’s IP via DNS 
• Implement a reverse proxy (such as Nginx or Traefik) 
• Secure the connection with an SSL certificate (e.g., Let’s Encrypt) 
• Fine-tune your variables:  
• N8N_HOST 

• N8N_PROTOCOL 

• WEBHOOK_URL 

If you are debating between the automated and hands-on approaches, here is a quick guide to help you decide. 

What to choose? 

Opt for manual Docker setup → Ideal for experienced users requiring intricate customization and absolute control over their stack. 

Opt for Bluehost one-click install → Perfect for rapid deployment, ease of use, and eliminating terminal-based friction. 

Keeping your software current is essential for security and accessing new capabilities. 

How to update n8n in Docker? 

The update process is one of Docker’s benefits. You merely pull the latest image, reconstruct the container, and rely on your preserved volume to supply the historical data. 

Recommended update flow (using Docker Compose): 

• Pull the latest image: docker compose pull 
• Recreate containers: docker compose up -d 
• Clean old images (optional): docker image prune 

What occurs during this process: 

• Your workflows and logic remain completely untouched inside your persistent volume 

• Docker fetches the newest iteration of the n8n application 

• Your container is instantly rebuilt utilizing the fresh image 

Even with a perfect setup, you might encounter occasional roadblocks. Here is how to resolve them. 

How to troubleshoot common n8n Docker issues? 

Deploying n8n via Docker can sometimes yield minor roadblocks. The vast majority of these are straightforward to remedy once properly identified. 

1. Port already in use 

Occasionally, port 5678 may already be occupied by a different application on your host machine. This will definitively block n8n from launching. 

How to fix it 

Docker run adjustment: 

Simply alter the external (host-side) port while preserving the internal container port. 

-p 5679:5678  

Docker Compose adjustment: 

"5679:5678"  

Afterward, you can access your platform at: 

• http://localhost:5679 

• http://YOUR_SERVER_IP:5679 

If you route traffic through ana Nginx proxy, you can maintain standard ports like 443 (HTTPS) while shifting the internal routing behind the scenes. 

2. Data loss after restart 

Experiencing missing credentials or vanished workflows after a reboot indicates a fundamental flaw in how your data is being retained. 

This is almost always the consequence of omitting a persistent volume from your configuration. 

How to fix it:

Verify that your volume mappings are correctly structured. 

Correct mapping (Docker run): 

-v n8n_data:/home/node/.n8n  

Correct mapping (Docker Compose): 

n8n_data:/home/node/.n8n  

This guarantees that your: 

• workflows 

• credentials 

• environment settings 

remain completely safe following any container restart. 

Note: 

If you previously designed workflows without a mapped volume, those assets might still reside within the dormant container. You may have to extract them manually before overhauling your setup. 

3. Container not starting 

A container that repeatedly fails to initialize usually points to a syntactical or configuration-based error. 

Typical culprits include: 

• Formatting errors within the Docker Compose file (invalid YAML) 

• Mistyped environment variables 

• Failed database connections (if utilizing PostgreSQL) 

• Strict permission constraints on mounted host directories 

How to check and fix:

Assess if the container is attempting to run: 

docker compose ps  

Scrutinize the recent logs for fatal errors: 

docker compose logs --tail=200  

Examine the raw container metadata: 

docker inspect n8n  

What to look for:

Look out for directory permission lockouts on your host machine. 

Scan for prominent error flags in the container output logs. 

Double-check for misspelled or totally omitted variables. 

Ensure your external database (like PostgreSQL) is accessible and accurately linked. 

Once your setup is stable, it is time to optimize it for serious, heavy-duty workloads. 

What are the best practices for running n8n in production 

Operating n8n professionally requires more than just achieving a “running” status. It requires ensuring absolute reliability, securing your vital data, and fortifying your endpoints. 

Adhering to these industry best practices will cement your infrastructure’s stability. 

1. Use PostgreSQL instead of SQLite 

Out of the box, n8n generally leans on SQLite. While adequate for local trials, it heavily underperforms in enterprise scenarios. 

Why PostgreSQL excels: 

• Efficiently processes massive concurrent workflow executions 

• Drastically improves long-term stability and resilience 

• Scales gracefully alongside your expanding automation needs 

By honing the scalability of PostgreSQL, businesses can seamlessly manage expanding datasets and workloads, making it a pivotal aspect of modern database administration 

2. Enable regular backups 

Backups serve as your ultimate safety net in production. Failing to configure them jeopardizes your entire automation ecosystem. 

What to back up: 

• Your dedicated Docker volume (housing the core n8n data) 

• The operational database (PostgreSQL) 

Best practices: 

• Automate your backup scheduling with cron jobs 

• Offload your backups to distinct, isolated storage servers 

• Routinely test your restoration process to ensure file integrity 

This preparation guarantees a swift recovery during worst-case scenarios. 

3. Use restart policies 

Containers can unexpectedly crash or shut down during broader server updates. 

Appending this rule to your Compose file mitigates the risk: 

restart: unless-stopped  

What this does: 

• Instantly re-initializes n8n if it crashes abnormally 

• Guarantees the application revives following a full host machine reboot 

This hands-off approach ensures round-the-clock availability for your workflows. 

4. Monitor logs and performance 

Proactive monitoring prevents minor hiccups from cascading into major outages. 

What to monitor: 

• Ongoing container error logs 

• Memory consumption and CPU load 

• Success and failure rates of your active workflows 

Basic command: 

docker compose logs  

For mission-critical processes, implementing automated alerts via Slack or email is highly recommended. 

This diagnostic oversight allows you to intercept issues before they compromise your data. 

5. Secure access with authentication 

Leaving a production instance of n8n fully exposed to the public internet is a massive security hazard. 

Recommended steps: 

• Funnel traffic exclusively through a reverse proxy (like Traefik or Nginx) 

• Enforce strict HTTPS via SSL certificates 

• Lock down dashboard access using IP whitelisting 

• Never map port 5678 openly to the public web 

These layers of security shield your vital credentials from malicious actors. 

6. Create a basic runbook 

A functional runbook is an essential operational manual detailing exactly how to navigate crises. 

It should encompass: 

• Step-by-step restart procedures 

• Detailed data restoration protocols 

• Standardized update methodologies 

• Instructions for rotating compromised credentials 

Simply put, it serves as your emergency blueprint when systems inevitably break. 

By implementing these strategies, you will ensure a highly dependable automation platform. 

Final thoughts 

Deploying n8n via Docker reaches its full potential when paired with Docker Compose, yielding a deeply resilient and reproducible foundation. This framework guarantees that your automation suite remains incredibly simple to update, exceptionally secure, and reliably backed by persistent data storage. 

For enterprise-grade environments, prioritize robust SSL encryption and aggressive backup strategies. Utilizing a dedicated VPS gives you the essential horsepower and architectural freedom necessary to expand your automation operations beyond the constraints of shared hosting. 

Eager to begin your automation journey without the configuration headaches? Bypass the tedious setup by opting for a Bluehost self-managed VPS, providing a streamlined, one-click n8n installation to launch your automation powerhouse immediately. 

FAQs