Set Up Your Free Local n8n Lab

Build a free local n8n lab with Docker, WSL 2, and persistent workflows.

Introduction

30 Second Summary

Most automation ideas start as small experiments, yet online tools can introduce subscriptions or shared spaces before you are ready. A private place to test gives you room to break things safely.

In this project, you will turn your Windows PC into a free local automation lab that keeps your work between restarts. You will use WSL 2, Docker Desktop, and Docker Compose to run n8n Community Edition inside Linux containers.

What You'll Build

Your private n8n editor opens in Zen Browser with a recovered workflow that returns ready after a complete service restart.

By the end of this project, you'll have:

A working local n8n editor you can open at http://localhost:5678 from Zen Browser.
A runnable lab-check workflow named Archive Automation Lab Check that returns lab_status as ready whenever you execute it.
A repeatable stop and restart routine that reveals a service outage while preserving your owner account and workflow in a persistent volume.
Secret Mission: Use Docker Desktop to inspect the Compose app, identify the running container, and read live n8n logs.

Are there any prerequisites?

You need a supported 64-bit Windows PC with hardware virtualization enabled and at least 8 GB RAM. This project guides you through setting up WSL 2, Docker Desktop, Docker Compose, and n8n Community Edition.

Before We Start

This is your moment to commit to building a free local n8n automation lab before any setup begins. Naming why local and free matter gives the work ahead a clear purpose.

Prepare Windows with WSL 2

Your free local n8n lab needs a Linux shell on your Windows PC. The supported one-line setup relies on that shell before the lab can run.

WSL 2 supplies the Linux environment through an Ubuntu distribution. This step confirms that Ubuntu uses WSL 2 before you build anything on top of it.

In this step, get ready to:

Check whether WSL is available on your Windows PC.
Complete Ubuntu's local account setup.
Verify that Ubuntu runs with WSL 2.

Check the WSL installation

Windows PowerShell reports whether WSL is available before you install anything. Administrator permissions allow Windows to add the required system components when they are missing.

Press the Windows key to open Windows search.
Type PowerShell into the search field.
Right-click Windows PowerShell in the search results.
Select the option that runs Windows PowerShell with administrator permissions.
Approve the Windows permission prompt.
Check whether WSL returns version details by running this command:

wsl --version

What Does This Command Check?

The wsl command communicates with Windows Subsystem for Linux.
The --version option requests details about the installed WSL components.

✔️ I see WSL version details

Good progress. Windows PowerShell is returning WSL version details. The next substep completes Ubuntu's local account setup.

ⓧ I do not see version details

Windows needs the current WSL installation. The standard installer also adds Ubuntu as the default Linux distribution.

The installation may sit quietly while Windows adds the required components. A pause in the terminal does not mean the process has failed.

Install WSL with Ubuntu by running this command:

wsl --install

What Does This Command Install?

The wsl command manages Windows Subsystem for Linux.
The --install option enables the required WSL components.
The same option installs Ubuntu as the default Linux distribution.

Restart Windows when the installer requests it.

Installation Not Completing?

Confirm that Windows PowerShell has administrator permissions.
Complete any pending Windows restart before trying the installation again.

Help me diagnose why WSL is not installing on my Windows PC. Compare your setup with Microsoft's official WSL installation guide.

ⓧ PowerShell cannot run WSL

An unavailable WSL command means Windows still needs the WSL components. The standard installer supplies those components with Ubuntu.

The installation may take some time while Windows changes system features. A quiet terminal during this process is expected.

Install WSL with Ubuntu by running this command:

wsl --install

What Does This Command Install?

The wsl command manages Windows Subsystem for Linux.
The --install option adds the required WSL components.
The same option installs Ubuntu as the default Linux distribution.

Restart Windows when the installer requests it.

WSL Still Unavailable?

Confirm that you approved the Windows permission prompt.
Complete any pending Windows restart before trying the installation again.

Help me troubleshoot an unavailable WSL command. Follow Microsoft's official WSL installation guide for the supported installation steps.

Create the Ubuntu account

Ubuntu finishes its setup the first time it opens. This first launch creates the local Linux account used inside the distribution.

The blank password line can look like the terminal has frozen. Ubuntu still records every keystroke while the line remains blank.

Press the Windows key to open Windows search.
Type Ubuntu into the search field.
Select Ubuntu from the search results.
Enter a Linux username when Ubuntu requests one.
Enter a Linux password when Ubuntu requests one.
Enter the same password when Ubuntu requests confirmation.

You have completed Ubuntu's first launch. You'll see a Linux shell prompt that accepts commands under your new username.

Ubuntu Not Opening?

Complete any Windows restart requested by the WSL installer.
Confirm that Ubuntu appears in Windows search after the restart.

Help me troubleshoot why Ubuntu is not opening after installing WSL.

Confirm Ubuntu uses WSL 2

An installed Ubuntu distribution can still use an earlier WSL generation. The VERSION column identifies the runtime used by each installed distribution.

Return to the administrator Windows PowerShell window from earlier.
Repeat the Windows search steps from the first substep if the restart closed that window.

Before you run the final check, which number do you expect to see beside Ubuntu?

List the installed Linux distributions with their WSL versions by running this command:

wsl.exe --list --verbose

What Does This Command Check?

The wsl.exe command manages WSL from Windows.
The --list option displays the installed Linux distributions.
The --verbose option includes each distribution's state and WSL version.

✔️ Ubuntu shows VERSION 2

You have the required result. The Ubuntu row shows 2 under VERSION. This confirms that the distribution uses WSL 2.

ⓧ Ubuntu shows VERSION 1

Ubuntu currently uses WSL 1. Converting the distribution gives it the WSL 2 runtime required by the local lab.

The conversion can take several minutes while Windows updates the distribution. A quiet PowerShell window during this process is normal.

Convert the Ubuntu distribution to WSL 2 by running this command:

wsl.exe --set-version Ubuntu 2

What Does This Command Change?

The --set-version option changes the runtime generation for one distribution.
The Ubuntu value selects the distribution you created.
The final 2 value selects WSL 2.

Before you check again, which value do you expect the VERSION column to show?

Verify the completed conversion by running the distribution list again:

wsl.exe --list --verbose

What Does the Second Check Prove?

The refreshed list reports the runtime version after conversion. The Ubuntu row now needs to show 2 under VERSION.

The Ubuntu distribution now uses WSL 2. Your Linux username and password remain available after the conversion.

Conversion Not Finishing?

Keep administrator Windows PowerShell open until the conversion finishes.
Confirm that the distribution name in the list is Ubuntu.

Help me troubleshoot an Ubuntu conversion from WSL 1 to WSL 2.

Ubuntu Row Missing?

A missing Ubuntu row means the distribution has not completed its first launch. Return to the Ubuntu account substep to finish that setup.

Help me find why Ubuntu is missing from the WSL distribution list.

That is the Windows foundation ready. Ubuntu is installed with a local account and runs with WSL 2.

Your Linux environment is ready. Next up, you will install Docker Desktop and connect it to Ubuntu.

Install and Verify Docker Desktop

Your Ubuntu distribution now runs on WSL 2. This gives Windows the Linux shell required by the local installation process.

The next gap is the container runtime that n8n needs. Docker Desktop supplies that runtime on Windows. It also includes Docker Compose for managing the services in your lab.

In this step, get ready to:

Install Docker Desktop 4.98.0 with the WSL 2 backend.
Enable Docker Desktop integration for Ubuntu.
Verify Docker Engine plus Docker Compose inside Ubuntu.

Install Docker Desktop

This project pins Docker Desktop to version 4.98.0. A version check reveals whether you can continue with an existing installation or need the installer.

Why Docker Desktop for this lab?

n8n directs new local installations toward Docker because its npm installation path is being retired. Docker Desktop provides the Windows engine plus the Compose tooling required by the local setup.

Its WSL 2 integration lets Ubuntu control Linux containers while Docker Desktop manages the underlying runtime. That combination gives the later n8n installer the environment it expects.

Return to the PowerShell window from the previous step.
Check whether Docker Desktop is already installed by running this command:

docker desktop version

What does this command check?

The docker desktop version command reports the installed Docker Desktop release. Its result determines which installation path you need.

Choose the tab that matches your PowerShell result.

✔️ I see the required version

Your version check shows Docker Desktop 4.98.0. The installed release is ready for the shared startup steps below.

ⓧ I see an older version

An older release puts your lab on a different Docker Desktop build. Updating to 4.98.0 keeps your environment aligned with this project.

Switch back to Zen Browser from earlier.
Open the Docker Desktop release notes in Zen Browser.
Select the Windows download under the 4.98.0 heading that matches your processor architecture.

Windows can display a permission request when the installer starts. Approving that request allows the installation to continue.

Run Docker Desktop Installer.exe from your Downloads folder.
Approve the Windows permission request if it appears.
Select the recommended per-user installation mode.
Select the WSL 2 backend on the Configuration page.
Finish the installation wizard.

ⓧ Command not found

PowerShell cannot find Docker Desktop because it has not been installed. The official release package adds the application plus its command-line tools.

Switch back to Zen Browser from earlier.
Open the Docker Desktop release notes in Zen Browser.
Select the Windows download under the 4.98.0 heading that matches your processor architecture.

Windows can display a permission request when the installer starts. Approving that request allows the installation to continue.

Run Docker Desktop Installer.exe from your Downloads folder.
Approve the Windows permission request if it appears.
Select the recommended per-user installation mode.
Select the WSL 2 backend on the Configuration page.
Finish the installation wizard.

The subscription terms screen can feel like a purchase prompt. Docker Desktop Personal costs $0 for eligible personal learning use.

Press the Windows key to return to Windows search.
Type Docker Desktop into the search field.
Press Enter to start Docker Desktop.
Accept the subscription terms when the terms screen appears.
Return to the PowerShell window from earlier.
Confirm the installed release by running the version check again:

docker desktop version

What confirms the installation?

This check reads the Docker Desktop release installed on Windows. It gives you a direct confirmation before you connect Ubuntu to the runtime.

You should see version 4.98.0. That confirms the pinned Docker Desktop release is installed and responding.

Installer not completing?

Confirm that the downloaded file is named Docker Desktop Installer.exe.
Confirm that Ubuntu still shows a VERSION value of 2 in the WSL distribution list.
Confirm that hardware virtualization remains enabled in your PC's BIOS or UEFI settings.

Help me diagnose why Docker Desktop is not installing or starting on my Windows PC. You can also search the Docker Community Forums for hardware-specific guidance.

Enable Ubuntu integration

Docker Desktop is running on Windows. WSL Integration makes its Docker commands available inside your Ubuntu distribution.

Select the Settings icon in the Docker Desktop Dashboard header.
Select Resources in the left sidebar.
Select WSL Integration.
Enable integration for Ubuntu.
Select Apply.
Leave Docker Desktop running in the background.

You should see Ubuntu remain enabled after Docker Desktop applies the setting. The distribution can now connect to the Windows-hosted Docker runtime.

Why does Ubuntu need integration?

WSL Integration connects the Docker commands inside Ubuntu to Docker Desktop's engine. This lets the Linux shell create and manage containers without a second Docker installation inside the distribution.

Verify Docker from Ubuntu

The final check confirms that Ubuntu can reach both the Docker engine and the Compose plugin. This is the exact toolchain the n8n setup uses in the next step.

Press the Windows key to return to Windows search.
Type Ubuntu and press Enter to return to its terminal.

You should see your Linux prompt again. Before you run the checks, do you expect Ubuntu to reach only the Docker client or both the client and server?

Verify Docker Engine and Docker Compose from Ubuntu by running these commands:

docker version
docker compose version

What do these commands prove?

The docker version command checks the Docker client inside Ubuntu. It also requests information from the running server.
The docker compose version command confirms that the Compose plugin is available from the same terminal.

You should see Docker client information. You should also see Docker server information.

The second command prints a Compose version. That is the bridge complete: Ubuntu can now control the container runtime that powers your local lab.

Ubuntu cannot reach Docker?

Confirm that Docker Desktop is still running on Windows.
Return to WSL Integration in Docker Desktop if Ubuntu cannot reach the engine.
Confirm that the Ubuntu integration switch remains enabled.

Help me troubleshoot Docker access from Ubuntu.

Your Windows container environment is ready. Next up, you will launch n8n and turn this infrastructure into a working automation lab.

Launch n8n and Build a Lab Check

Your WSL 2 environment can now run Linux containers through Docker Compose. This step turns that foundation into your local automation lab.

A running service becomes useful when it produces a result you can inspect. You will launch n8n Community Edition. A two-node workflow will prove that the editor works.

In this step, get ready to:

Install n8n Community Edition through Docker Compose.
Create your local n8n owner account.
Build a workflow that returns a visible lab status.

Run the official n8n installer

The official installer generates the local configuration under ./n8n. It also starts the services that make the editor available in your browser.

Return to the Ubuntu terminal from the previous step.
Confirm that the terminal is currently in your Linux home folder.
Create the ./n8n configuration and start the local stack by running this official installer command:

curl -fsSL https://get.n8n.io | sh

What does this installer do?

The installer creates the ./n8n configuration folder.
It generates ./n8n/.env, ./n8n/compose.yml, and ./n8n/searxng-settings.yml.
Docker Compose launches the local services described by the generated configuration.
The n8n-data persistent volume keeps your local n8n state outside the containers.

The first run can take several minutes while Docker downloads the required images. A quiet terminal during this download does not mean the setup is broken.

Wait while the installer downloads the container images.
Confirm that the installer reports n8n version 2.46.4.
Confirm that the installer reports n8n is running at http://localhost:5678.
Confirm that the installer identifies the generated configuration under ./n8n.

The biggest startup wait is behind you. Your n8n services are now running from the generated ./n8n configuration.

Installer shows a different version?

Stop here if the installer reports anything other than 2.46.4.
Run the same installer command again when the stable-release lookup is reachable.

If the installer still selects a different version, help me diagnose the n8n installer output.

Create your local owner account

The signup screen creates the owner account for this self-hosted editor. This account controls access to your local workspace.

Switch back to Zen Browser from earlier.
Enter http://localhost:5678 in the address bar.

You should see the n8n signup screen. This credential belongs to your local lab, so creating it does not sign you up for a hosted n8n plan.

Enter the owner details requested by the signup screen.
Create a password with at least eight characters, one number, and one capital letter.
Submit the signup form to create the owner account.

You should now be inside the local n8n editor. Your owner account is ready to create workflows.

Signup screen not loading?

Confirm that the installer terminal still reports that n8n is running.
Confirm that Docker Desktop remains running in the background.
Refresh http://localhost:5678 after the services finish starting.

If the signup screen remains unavailable, help me troubleshoot my local n8n signup page.

Build and run the lab check

The Manual Trigger starts the workflow when you choose to test it. The Edit Fields (Set) node creates a fixed result that is easy to verify.

Select Personal.
Select Create workflow.

You should see a blank workflow canvas in your Personal workspace.

Select the workflow name at the top of the editor.
Enter Archive Automation Lab Check as the new name.
Select Add first step....
Add the Manual Trigger node.

You should see the Manual Trigger node on the canvas. This gives your lab check a manual starting point.

Select the connection control on the Manual Trigger node.
Add Edit Fields (Set) as the next node.

You should see a connection between both nodes. Data now has a path from the trigger to the output field.

Select the Edit Fields (Set) node on the canvas.
Select Manual Mapping.

The node is now ready for a field that you control directly.

Select Add Field.
Keep Fixed selected for the field value.

You should see a mapping row for the fixed output.

Enter lab_status as the field name.
Enter ready as the fixed value.

The mapping now pairs lab_status with ready.

The editor usually needs 1 to 5 seconds to autosave the draft. That short pause protects your workflow before the test.

Wait a few seconds for n8n to autosave the workflow.

Before you run the workflow, what value do you expect the Edit Fields output to contain?

Select Execute Workflow.

Both nodes should show successful execution. The Edit Fields output should contain lab_status with the value ready.

You now have your first working automation result. The local lab accepts a workflow execution and returns a result you can inspect.

What does this result prove?

The Manual Trigger proves that the editor can start a workflow on demand.
The Edit Fields node proves that data can move through the connected workflow.
The n8n-data volume stores your local owner account.
The same volume preserves the saved workflow for later restarts.

Output missing lab_status?

Confirm that the Manual Trigger connects directly to Edit Fields (Set).
Reopen the Edit Fields (Set) node.
Confirm that Manual Mapping is selected.
Confirm that the field uses the fixed value ready.

If the workflow still does not return the field, help me troubleshoot my n8n lab-check workflow.

Your local n8n lab is running with a saved workflow that returns a visible result. Next, you will stop the services deliberately and observe what changes when the stored state remains but the containers are unavailable.

Stop the Lab and Observe the Outage

Your local n8n lab has already returned lab_status as ready from Archive Automation Lab Check. Now you will test its service lifecycle by deliberately stopping the Docker Compose stack.

The generated folder and a persistent volume hold the lab's state. This step tests whether stored data alone can keep the editor available after the containers stop.

In this step, get ready to:

Stop the n8n Compose services without deleting the saved lab state.
Confirm that Zen Browser can no longer reach the local editor.

Stop the Compose services

Stopping the lab can feel drastic. Your saved owner account and workflow remain in the persistent volume.

Before you stop the stack, do you think the saved workflow can keep the editor available on its own?

Switch back to the Ubuntu terminal from earlier.
Stop the n8n Compose services by running this command:

docker compose -f ./n8n/compose.yml down

What does this command do?

The docker compose command manages the Compose project.
The -f ./n8n/compose.yml option selects the generated n8n configuration.
The down subcommand stops and removes the active services.
The command does not include -v, so the n8n-data volume remains intact.
The command does not remove the ./n8n folder.

Wait for the Ubuntu prompt to return.

You'll see Docker Compose report that the running services have stopped and been removed. The controlled shutdown is complete without deleting your saved state.

Compose Cannot Stop the Services?

Confirm that Docker Desktop from earlier is still running.

Ask for help with the shutdown command.

Test the editor connection

The Compose services have stopped. The existing browser tab now gives you a direct test of whether stored state provides service availability.

Before you refresh, do you expect the editor to load from its saved data?

Switch back to the existing n8n tab in Zen Browser.
Refresh http://localhost:5678.

Zen Browser cannot load the n8n editor. This outage is the intended result.

What Did the Outage Prove?

The ./n8n folder keeps the generated configuration. The n8n-data volume keeps the local owner account and saved workflow.

Stored state cannot answer browser requests by itself. The n8n editor needs running containers.

You have now felt the difference between saved state and service availability. Next, you will restart the same Compose project to test whether your account and workflow return.

Restart n8n and Prove Persistence

The outage you created proved that stored files do not make n8n available. Now you will use Docker Compose to recreate the stopped services from the retained configuration.

The open question is whether the local owner account survived the removal of its containers. The saved workflow faces the same test.

The persistent volume should carry saved state into replacement containers. This restart tests storage against availability.

In this step, get ready to:

Restart the stopped Compose project.
Recover the saved n8n workspace.
Execute the lab-check workflow to test persistence.

Reuse the retained Compose project

The retained ./n8n/compose.yml describes the services needed for your lab. The start command reuses the generated project configuration.

Switch back to the Ubuntu terminal from earlier.
Recreate the n8n services from the retained configuration by running this command:

docker compose -f ./n8n/compose.yml up -d

What does this command do?

docker compose reads the generated project definition.
up -d recreates the stopped services in the background.
The retained n8n-data volume reconnects the saved n8n state to the recreated services.

Wait for the command to return to the Ubuntu prompt.

Docker reports the service startup before the prompt returns. The n8n services now run in the background.

Did the services fail to start?

Confirm Docker Desktop from earlier is still running.
Confirm your terminal is in the Ubuntu Linux home folder that contains the n8n folder.
Check that the restart command uses ./n8n/compose.yml exactly.

Help me troubleshoot why my retained n8n Compose project will not restart.

Recover your saved n8n workspace

Starting the services restores the application process. Your browser now reveals whether its saved state returned with it.

Return to the n8n tab in Zen Browser from earlier.
Refresh http://localhost:5678.

You should see the local n8n interface load again. The outage has ended because the services are running.

The same local credentials reconnect you to the owner account stored in the retained volume.

Sign in with the same local owner account when n8n prompts you.
Select Personal from the n8n workspace navigation.
Open Archive Automation Lab Check from your saved workflows.

You should see the saved workflow on the editor canvas. Its return proves that container recreation preserved the workflow record.

Still unable to reach n8n?

Wait briefly before refreshing the page again.
Confirm Docker Desktop from earlier is still running.
Return to the Ubuntu terminal from earlier to check that the restart command completed without an error.

Help me troubleshoot why n8n is still unavailable after restarting its Compose services.

Prove persistence with the lab check

The workflow title proves its record survived. A successful execution gives stronger evidence by exercising the recovered node configuration.

Confirm Manual Trigger connects to Edit Fields (Set) on the workflow canvas.
Select Edit Fields (Set) to inspect its recovered settings.

You should see Manual Mapping. Under Fields to Set, you should see lab_status set to ready.

Before you run the workflow, do you expect both recovered nodes to execute successfully after the containers were recreated?

Select Execute Workflow.

You will see both nodes show successful execution. The Edit Fields output contains lab_status with the value ready.

That is the recovery proven: your recreated containers serve the same saved lab state. Your local automation foundation survives routine service recreation.

What did the recovery prove?

The retained Compose configuration restored the processes that make the editor available.

The n8n-data volume restored the owner account plus the saved workflow state. Service availability can change while persistent data remains intact.

Secret mission

Inspect the Running Stack

Your n8n editor proves the workflow works. In this mission, you will identify its running services in Docker Desktop. You will trace port 5678 from the live logs to the container mapping.

Clean Up Your Resources

Your next choice is whether the local n8n lab stays running, pauses for later, or is deleted. Eligible personal learning use has no recurring cloud charge.

Cost warning

For eligible personal learning use, Docker Desktop Personal costs $0. Larger organizations or government entities may require a paid subscription.

The lab still uses local disk space. Running containers use memory. They also use CPU.

Resources you used:

The running Docker Compose services that make the editor available at http://localhost:5678.
The ./n8n configuration folder containing compose.yml, .env, and searxng-settings.yml.
The n8n-data Docker volume that stores your local owner account and Archive Automation Lab Check workflow.

What stays installed?

These cleanup options target the lab created inside Ubuntu. WSL 2 stays installed.

Docker Desktop also stays installed. These tools can support your later local projects.

Keep everything running

No action is needed. This option keeps your local editor available for active work.

Keep Docker Desktop running in the background.
Leave the n8n Compose services running.
Return to http://localhost:5678 in Zen Browser whenever you want to use the lab.

Pause - I'll come back to this later

Shut down the running processes to free local memory. Your saved lab state remains available for the next restart.

Return to the Ubuntu terminal from earlier.
Stop the running Compose services while preserving your saved lab state by running:

docker compose -f ./n8n/compose.yml down

What does this command preserve?

This command stops the services that make n8n available. It preserves the ./n8n folder.

The n8n-data volume also remains intact. Your owner account and workflow are ready for the next restart.

Return to Zen Browser from earlier.
Refresh http://localhost:5678.

Zen Browser can no longer load the n8n editor. This confirms that the local services have stopped.

Still seeing the editor?

Wait a few seconds for the services to finish stopping.
Refresh http://localhost:5678 again.
Check that the Ubuntu terminal reported that the Compose services were removed.
Help me troubleshoot why my local n8n editor still loads after stopping the Compose services.

Delete - I don't want to use this again

This option removes the local lab for a fresh start.

The deletion is permanent. Your owner account and workflow cannot be recovered afterward.

Return to the Ubuntu terminal from earlier.
Delete the Compose resources plus the n8n-data volume by running:

docker compose -f ./n8n/compose.yml down -v

What does this command delete?

The -v option permanently deletes the persistent n8n data volume. This removes the local owner account.

It also removes saved workflows, credentials, and execution history. The running Compose resources are removed at the same time.

Remove the generated ./n8n folder by running:

rm -rf ./n8n

What does this command delete?

This command removes the generated configuration folder from your Ubuntu home folder. The deleted files include compose.yml, .env, and searxng-settings.yml.

Return to Docker Desktop from earlier.
Select Containers in the left sidebar.
Confirm that the Compose app created from the n8n folder is no longer listed.
Refresh http://localhost:5678 in Zen Browser.

Zen Browser can no longer load the editor. Your local n8n lab has been removed.

Cleanup command failed?

Confirm that Docker Desktop is still running before you retry the first command.
Confirm that the Ubuntu terminal is in the Linux home folder containing ./n8n.
Help me safely finish deleting my local n8n lab.

Nice Work!

You did it! You built a free local n8n automation lab that runs inside Linux containers on your Windows PC.

You've learned how to:

Prepared WSL 2 with Ubuntu for the lab. Verified Docker Desktop with Docker Compose from Ubuntu.
Built Archive Automation Lab Check in the n8n workflow editor. Ran it to confirm that lab_status returned ready.
Stopped the Compose services to observe a deliberate outage. Restarted the stack to recover the saved owner account and workflow from the persistent n8n-data Docker volume.
Secret Mission: Inspected the running Compose app in Docker Desktop. Traced the n8n container through its status, live logs, search results for 5678, and port mapping.

Ready to quiz yourself?