The Ultimate Guide to Self-Hosting for Beginners: Home Lab & Docker Essentials

Docker has made it possible to run over fifteen different self-hosted services on old hardware, not just expensive servers. (homeio.app)

Self-hosting used to be the territory of IT veterans with racks of servers humming in the basement. Now, according to homeio.app, a mini PC, old desktop, NAS, Raspberry Pi, or even a repurposed laptop can serve as the backbone of your first home lab. The entry cost is as minimal as the hardware you already have.

Self-Hosting Is About Control, Not Hardware

Most people get this wrong: self-hosting is not about having the best gear, but about reclaiming privacy and flexibility without breaking the bank. Recent data from homeio.app shows that repurposed hardware, like an old PC or mini PC, allows you to start for almost nothing. This means you can avoid new hardware investments entirely. The real benefit? You control your applications, your data, and your uptime, without sending your information to third-party servers. If you believed you needed a server room, you can let that myth die here.

Worked Example: Turning an Old Laptop Into a Home Lab

To illustrate the low barrier to entry, let's walk through repurposing an old laptop:

1. Assess the Hardware: Ensure the laptop has at least 4GB of RAM and some available storage (even 128GB is enough to start).
2. Install Ubuntu Server 22.04 LTS: Download the ISO, create a bootable USB, and install. Minimal install saves resources.
3. Install Docker: Use the official Docker install script from docker.com.
4. Deploy a Container: Run docker run hello-world to verify installation. Try deploying Jellyfin or Nextcloud next.
5. Access Services: Connect on your local network to see your apps in action.

This example demonstrates how even outdated, unused gear can become the foundation of your home server.

Self-Hosted Tools Compared — Live Stats (verified 2026-11-02)

Tool	Docker Hub pulls	GitHub stars	Last update
Nextcloud	1.0B	37,393	2026-11-02
Jellyfin	454.6M	58,913	2026-11-01
Pi-hole	1.0B	61,626	2026-11-02
Tailscale	189.5M	38,504	2026-11-02
Home Assistant	802.5M	91,905	2026-11-02
Immich	—	117.9K	2026-11-02

Live figures pulled directly from the official Docker Hub and GitHub APIs on 2026-11-02. We re-verify them on every update so the comparison stays current.

→ See also: How to Start a Home Lab for Beginners?

Docker Is the Beginner’s Friend

Docker packages applications and their dependencies into containers, ensuring consistent environments across different systems. This isolation prevents resource conflicts and dependency issues. (techradar.com)

This is what actually works. Not the fluffy advice you see everywhere. Docker takes the pain out of dependency hell. If you’ve ever broken an app by upgrading the wrong library, containers are your safety net. You’ll notice you can move services between machines or try out new ideas with almost zero risk. For beginners, this is the difference between constant frustration and a home lab that just works.

Step-by-Step: Deploying Your First Docker Container

1. Install Docker:
   • On Ubuntu, run:

     curl -fsSL https://get.docker.com -o get-docker.sh
     sudo sh get-docker.sh
     

2. Run a Test Container:
   • docker run hello-world confirms Docker is working.
3. Find a Useful Image:
   • Search Docker Hub for 'nextcloud' or 'jellyfin.'
4. Deploy Nextcloud:
   • docker run -d -p 8080:80 nextcloud
5. Access the Service:
   • Visit http://localhost:8080 on your browser to finish setup.

Docker documentation and community guides provide troubleshooting help for any hiccups.

The Essential Hardware Checklist for 2026

A mini PC, old desktop, NAS, Raspberry Pi, or dedicated server can serve as the host for a home lab. This flexibility allows users to repurpose existing hardware, making the initial investment minimal. (homeio.app)

If you have a Raspberry Pi gathering dust, you’re already ahead. Old laptops can pull their weight too. The point is, there’s no minimum spend required. Focus on what you have and scale up only when your needs outgrow your current setup. The initial step is always to check your drawers before checking your bank account.

Hardware Options in Detail

• Mini PCs: Compact, low-power, often silent. Good for 24/7 operation in a small space.
• Old Desktops/Laptops: Abundant and cheap. May use more power but are sufficient for most beginner setups.
• Raspberry Pi: Popular for its low cost and low power draw. Great for learning, but limited for heavy workloads.
• NAS (Network Attached Storage): Some models support Docker natively, making them ideal for storage-heavy setups.
• Dedicated Servers: Necessary only for large, resource-intensive deployments.

Picking the Right Operating System: Simplicity Wins

There are many ways to run a home lab, but most beginners reach for Ubuntu Server 22.04 LTS. It’s stable, well-documented, and widely used for Docker hosting. A simple OS means less troubleshooting. When you’re learning, every hour saved on OS quirks is an hour gained for building your stack. Ubuntu’s massive community provides quick answers to almost every issue, so you’re rarely stuck for long.

Operating System Trade-Offs

• Ubuntu Server 22.04 LTS: Most popular for its balance of stability and up-to-date packages.
• Debian: Even more stable, but packages can be older.
• Fedora/CentOS: Useful for those who prefer RPM-based distributions, but community support for Docker may vary.
• Windows: Possible, but Docker runs best natively on Linux.
• Specialized OSes (OpenMediaVault, TrueNAS): Good for storage-focused home labs, but may have limitations for broader Docker deployment.

→ See also: Building a Home Lab from Scratch

Why Docker Compose Is a Game-Changer

Docker Compose simplifies the management of multi-container applications by allowing users to define services, networks, and volumes in a single file, streamlining the deployment process. (selfhostedguides.com)

No more running individual containers by hand. Compose means one command to bring your whole environment up or down. It’s the difference between manual assembly and hitting a “start” button. The main thing: read your YAML files carefully and keep your configurations under version control. Debugging YAML is an art, but once you get it, your deployments become push-button simple.

Compose for Real-World Apps: Example YAML

version: '3.8'
services:
  nextcloud:
    image: nextcloud
    ports:
      - "8080:80"
    volumes:
      - nextcloud_data:/var/www/html
volumes:
  nextcloud_data:

This example launches Nextcloud with persistent storage. Add more services by expanding the services block.

The Most Popular Self-Hosted Apps for Beginners

Services like Jellyfin, Immich, Pi-hole, Home Assistant, and Nextcloud are commonly self-hosted. These applications cater to media streaming, photo management, network security, home automation, and cloud storage needs. (homeio.app)

If you’re new, start with one or two: Jellyfin for media, Nextcloud for storage, Pi-hole to block ads network-wide. Each of these comes with active communities and clear Docker images, so you’re not left guessing. The trick is to pick services you’ll actually use, not just what looks cool on a dashboard.

Application Deep Dive

• Jellyfin: Open-source media server. Streams local movies and TV to all devices.
• Nextcloud: Private cloud storage and file sharing. Replaces Dropbox or Google Drive.
• Pi-hole: Network-wide ad blocker. Improves browsing speed and privacy.
• Home Assistant: Automates smart home devices. Integrates with hundreds of brands.
• Immich: Modern photo management, perfect for private photo hosting.

Step-by-Step: Deploying Jellyfin with Docker Compose

version: '3.8'
services:
  jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    ports:
      - '8096:8096'
    volumes:
      - ./config:/config
      - ./media:/media
    restart: unless-stopped

Run with docker-compose up -d and access via http://localhost:8096.

Security: The Real Risks and the Real Solutions

Exposing self-hosted services to the internet can introduce vulnerabilities. It's crucial to implement robust security practices to mitigate potential risks.

Utilizing zero-trust mesh VPNs like Tailscale or Cloudflare Tunnels provides encrypted remote access to internal home lab dashboards without exposing home IP addresses directly to the internet. (findtutu.com)

This is non-negotiable. Do not open ports to the world. Secure tunnels or VPNs keep your home IP out of the public eye. If you skip this, you’re not running a home lab, you’re running a honeypot for attackers. Tailscale, in particular, takes five minutes to set up and closes the biggest security hole most beginners leave open.

Security Checklist

• Use strong, unique passwords for each service.
• Keep all software—Docker, OS, applications—up to date.
• Use Tailscale for remote access. Avoid port forwarding wherever possible.
• Regularly audit which containers are running and what ports are exposed.
• Backup your data regularly.

→ See also: What Hardware Do I Need for a Home Lab

The Learning Curve: Why Docker Is Worth It

While Docker simplifies application deployment, beginners may face a learning curve in understanding containerization concepts and Docker commands.

You’ll probably hit a wall in your first week. Most people do. The key is persistence—Docker’s documentation and forums are extensive for a reason. Every concept you master saves you hours down the line. The pain of learning once is less than the pain of fixing broken installs every month.

Common Docker Concepts to Master

• Images: Blueprints for containers.
• Containers: Running instances of images.
• Volumes: Persistent data storage for containers.
• Networks: How containers communicate.
• Compose: Managing multi-container setups.

Troubleshooting Your First Error

Docker error messages can be cryptic. When in doubt:

1. Check container logs: docker logs <container_name>
2. Look for YAML formatting mistakes (indentation is critical).
3. Google the error with your app name—chances are, someone has solved it.
4. Ask in community forums (see the Community section below).

Real Cost Savings: Why Self-Hosting Makes Sense in 2026

Repurposing an old PC or mini PC for a home lab setup can be a cost-effective solution, reducing the need for new hardware investments. (homeio.app)

You’ll see endless arguments about the cloud versus local hosting, but the numbers are simple: cloud storage and streaming subscriptions add up fast. Running your own stack on old gear puts that money back in your pocket. And when you need to scale, upgrading just one part—like adding a bigger drive—is cheaper than jumping to a new paid tier.

Example: Comparing Cloud and Self-Hosting Costs

• Cloud storage (e.g., Dropbox, 2TB): Ongoing monthly fee.
• Self-hosted Nextcloud (using existing hardware): Zero ongoing fee, small additional electricity cost.
• Streaming services (e.g., Netflix): Monthly subscription.
• Self-hosted Jellyfin (with local library): No subscription, one-time setup.

Over a year, even with modest use, self-hosting can save hundreds of dollars.

The Community: Your Most Undervalued Resource

The self-hosting community is vast and active, offering forums, tutorials, and guides to assist newcomers in troubleshooting and optimizing their setups.

No matter where you get stuck, someone has solved it before. The best advice: ask for help early and often. There’s no shame in being the hundredth person with a Docker Compose typo. Community support is the single biggest reason beginners actually finish their first home lab project.

Where to Find Help

• Reddit: r/selfhosted, r/homelab
• Discord servers: Many projects have active chat rooms.
• Project forums: Each major app has its own support forum.
• Documentation: Official docs for Docker, Ubuntu, and each app are usually thorough and beginner-friendly.

→ See also: Self Hosting Benefits

Scalability: Growing Your Lab Without Growing Your Headache

A well-designed home lab can be easily expanded by adding more containers or upgrading hardware components, allowing users to scale their self-hosting environment as needed.

Docker makes scaling as simple as copying a YAML file or plugging in a bigger drive. It’s not about building the biggest stack right away. It’s about growing when you need it, without rewriting everything from scratch. Add a new app, test it, and keep what works.

Scaling Strategies

• Add More Containers: Each service is a container—grow your stack one service at a time.
• Upgrade Storage: Swap in a larger drive as your needs grow.
• Move to Bigger Hardware: When you outgrow your old PC, migrate containers to a more powerful machine.
• Network Expansion: Add VLANs or subnets to isolate services as complexity increases.

Common Misconceptions: What Beginners Get Wrong

Many believe that setting up a home lab necessitates high-end servers. In reality, repurposed hardware like old PCs or mini PCs can suffice for most beginner setups. (homeio.app)

While Docker introduces new concepts, its user-friendly tools and extensive documentation make it accessible to beginners. With proper security measures, such as using VPNs and regularly updating software, self-hosting can be secure and private. If you think you can’t do this because you’re not a sysadmin, you’re missing the point.

More Myths Busted

• Myth: Self-hosting is unreliable. Reality: With Docker and regular updates, it’s often more reliable than cheap cloud tiers.
• Myth: You need to know Linux inside-out. Reality: You’ll pick up what you need as you go; community guides fill the gaps.
• Myth: Self-hosting is a huge time sink. Reality: The initial setup takes time, but maintenance is minimal if you automate with Compose.

The Legal and Compliance Angle

Hosting certain applications or data may have legal implications, especially concerning data protection laws. Users should be aware of and comply with relevant regulations.

Don’t ignore this. If you’re hosting sensitive or regulated data, check your local laws first. Personal projects rarely cross a line, but the minute you let others use your services, the stakes go up. It’s not about paranoia—it’s about not getting burned by something simple.

Typical Compliance Issues

• GDPR/Privacy Laws: If you host data for others, you may need to comply with privacy regulations.
• Copyright: Hosting media you don’t own or have rights to can create legal risk.
• Terms of Service: Check the TOS for any third-party service integrations.

→ See also: Getting Started with Raspberry Pi for Self-hosting

Home Lab Management Dashboards: Homeio in Practice

Homeio is a dashboard that simplifies the management of Docker applications in a home lab setup.

You want visibility without complexity. Homeio lets you monitor, start, and stop containers from a single interface. For beginners, this is the difference between “what’s running?” and “I broke my lab.” A dashboard is not a crutch—it’s your cockpit.

Homeio Features

• Simple web interface for starting/stopping containers.
• Visual monitoring of resource usage.
• Easy access to logs and error messages.
• Integration with Docker Compose stacks.

Key Tools Side-by-Side

Tool	Purpose	Cost
Docker	Containers/Deployment	Free
Homeio	Dashboard Management	Free
Tailscale	VPN/Secure Tunnels	Free
Ubuntu Server 22.04 LTS	Operating System	Free
Nextcloud	Cloud Storage	Free

Zero-Trust Networking: How to Keep Your Lab Safe in 2026

Utilizing zero-trust mesh VPNs like Tailscale or Cloudflare Tunnels provides encrypted remote access to internal home lab dashboards without exposing home IP addresses directly to the internet. (findtutu.com)

Here’s the thing nobody tells you: every port you open increases your attack surface. Zero-trust networking isn’t a buzzword—it’s insurance. Tailscale sets the VPN up for you, so you’re not writing iptables rules at 2 a.m. Paranoia is cheap; breaches are expensive.

Step-by-Step: Setting Up Tailscale

1. Install Tailscale on your server:
   • Follow official instructions for your OS.
2. Authenticate:
   • Use your Google, Microsoft, or GitHub account to join your device to your private mesh network.
3. Install Tailscale on your client devices:
   • Laptops, phones, tablets—repeat the process.
4. Access Home Lab Remotely:
   • Use the private Tailscale IP to connect securely from anywhere, without exposing public ports.

→ See also: Diy Home Server Ideas for Beginners

Docker Compose in Action: Real-World Example

Docker Compose simplifies the management of multi-container applications by allowing users to define services, networks, and volumes in a single file, streamlining the deployment process. (selfhostedguides.com)

Most people start with a basic docker-compose.yml for something like Nextcloud or Jellyfin. The structure is always the same: define your service, volumes, and networks. The best advice? Don’t copy random files from the internet without reading them. Your configuration is your blueprint—treat it with respect.

Example: Multi-Service Compose Stack

version: '3.8'
services:
  nextcloud:
    image: nextcloud
    restart: always
    ports:
      - 8080:80
    volumes:
      - nextcloud_data:/var/www/html
  db:
    image: mariadb
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: example
      MYSQL_DATABASE: nextcloud
      MYSQL_USER: nextcloud
      MYSQL_PASSWORD: nextcloudpass
    volumes:
      - db_data:/var/lib/mysql
volumes:
  nextcloud_data:
  db_data:

This stack launches both Nextcloud and a MariaDB database. Managing multiple related services is simple and repeatable.

The Role of Open Source in Home Labs

Open source applications like Nextcloud, Jellyfin, Pi-hole, and Home Assistant are the backbone of self-hosting for beginners. They provide transparent code, active communities, and regular updates. This openness lets you audit what’s running on your hardware, not just hope for the best. The main draw: you’re not locked in. If you don’t like a project’s direction, you can always switch to a fork or alternative.

Benefits of Open Source for Self-Hosting

• Transparency: Know exactly what code is running.
• Community-Driven: Features and fixes come from user feedback.
• No Vendor Lock-In: Switch or fork as you see fit.
• Frequent Updates: Security patches and new features are released quickly.
• Learning: Source code and documentation are available, aiding troubleshooting and customization.

Expanding Beyond the Basics: Where to Go Next

A well-designed home lab can be easily expanded by adding more containers or upgrading hardware components, allowing users to scale their self-hosting environment as needed.

Once you’re comfortable, adding a new service is as simple as another Compose block. Test, tweak, repeat. This modularity is the real secret to not burning out. If something breaks, you fix one container, not the whole system. Incremental change beats “big bang” upgrades every time.

Example Expansion: Adding Home Assistant

1. Add this to your Compose file:

  homeassistant:
    image: homeassistant/home-assistant
    container_name: homeassistant
    volumes:
      - ./hass_config:/config
    restart: unless-stopped
    network_mode: host

2. Run docker-compose up -d homeassistant.
3. Access at http://localhost:8123 and start integrating your smart devices.

→ See also: Affordable Hardware for Small Home Labs

Troubleshooting: How to Stay Sane When Things Break

The self-hosting community is vast and active, offering forums, tutorials, and guides to assist newcomers in troubleshooting and optimizing their setups.

Expect things to break. The trick is to document your changes and rollback when needed. Most errors are config problems, not fatal bugs. The best fix: ask in community forums, share logs, and learn from the responses. Nobody expects you to be an expert on day one, but everyone expects you to learn.

Troubleshooting Framework

• Isolate the Problem: Is it Docker, the OS, or the application?
• Check Logs: Both Docker and application logs provide clues.
• Rollback: If you use version control for your Compose files, revert to a known good state.
• Community Help: Provide context, Compose files, and exact error messages.

Real-World Example: Building a Mini Media Server Stack

Services like Jellyfin, Immich, Pi-hole, Home Assistant, and Nextcloud are commonly self-hosted. These applications cater to media streaming, photo management, network security, home automation, and cloud storage needs. (homeio.app)

Start with Jellyfin for movies and TV, add Pi-hole for better browsing, then throw in Nextcloud for cloud storage. You get a Netflix alternative, fewer ads, and Dropbox on your own hardware. The jump in control is immediate; the cost is just your time and a bit of learning.

Example Stack YAML

version: '3.8'
services:
  jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    ports:
      - "8096:8096"
    volumes:
      - ./jellyfin_config:/config
      - ./media:/media
    restart: unless-stopped
  pihole:
    image: pihole/pihole:latest
    container_name: pihole
    environment:
      TZ: 'America/New_York'
      WEBPASSWORD: 'yourpassword'
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "80:80"
    volumes:
      - ./pihole/etc-pihole:/etc/pihole
      - ./pihole/etc-dnsmasq.d:/etc/dnsmasq.d
    restart: unless-stopped
  nextcloud:
    image: nextcloud
    container_name: nextcloud
    ports:
      - "8080:80"
    volumes:
      - ./nextcloud_data:/var/www/html
    restart: unless-stopped

Automating with Docker Compose: The Next Step

Docker Compose simplifies the management of multi-container applications by allowing users to define services, networks, and volumes in a single file, streamlining the deployment process. (selfhostedguides.com)

Once you have more than three services, automation isn’t a luxury—it’s a necessity. A single docker-compose up -d brings everything online. Mistakes happen, but Compose lets you fix things fast and recover with a single command. This is how you spend less time administrating and more time actually using your home lab.

Scheduling Backups and Updates

• Use cron jobs to automate backups of Docker volumes.
• Use docker-compose pull and docker-compose up -d to update services with minimal downtime.

→ See also: How Much Does Self Hosting Cost

Case for Regular Backups

While Docker simplifies application deployment, beginners may face a learning curve in understanding containerization concepts and Docker commands.

The number one regret: not backing up before making changes. Docker makes it easy to snapshot volumes. Use that power. If you trash your setup, a restore is five minutes, not five hours. The difference between hobbyists and pros is how much data they’re willing to lose.

Backup Strategy Example

1. Stop containers: docker-compose down
2. Tar up your volumes: tar czf backup_nextcloud_$(date +%F).tar.gz ./nextcloud_data
3. Store backups offsite (external drive or cloud backup).
4. Restore by un-tarring and rerunning docker-compose up -d.

Monitoring and Maintenance

A healthy home lab runs quietly in the background. However, proactive monitoring and scheduled maintenance are key to long-term reliability.

Monitoring Tools

• Homeio: Visual resource monitoring, container status.
• Docker stats: CLI tool for real-time resource use.
• Prometheus/Grafana: Advanced users can integrate for historical data and alerts.

Maintenance Checklist

• Apply OS and Docker updates monthly.
• Check backup integrity quarterly.
• Review Compose files for deprecated features annually.

Trade-Offs in Self-Hosting

Every choice in your home lab involves trade-offs. Understanding these will help you build a setup that matches your needs.

Performance vs. Power Consumption

• Old desktops deliver more performance but use more energy than a Raspberry Pi or mini PC.
• NAS boxes are power efficient but may lack CPU for heavy workloads.

Simplicity vs. Flexibility

• Single-board computers (Raspberry Pi) are easy, but limited.
• Full desktops or servers are complex, but support more demanding services.

Security vs. Accessibility

• Exposing services increases convenience but also risk.
• VPNs and tunnels add a layer of setup, but are much safer.

→ See also: Self Hosting Ideas

Edge Cases: What If…?

What if my hardware dies?

• Keep Compose files and configs on external storage or in the cloud.
• Restoring to new hardware is as simple as reinstalling Docker and running your Compose file.

What if I want to move my lab offsite?

• Use Tailscale to keep your private network connected, no matter where the server lives.

What if an app I want isn’t on Docker Hub?

• Look for community images or consider building your own Dockerfile.
• Request support in project forums; many maintainers add Docker support based on user demand.

Advanced: Integrating Cloud Services

While the focus is local hosting, hybrid models can offer the best of both worlds.

• Cloud Backups: Use cloud storage to back up critical Docker volumes.
• DNS: Use dynamic DNS to keep your home lab accessible as your IP changes.
• Hybrid Authentication: Some projects support OAuth or SSO for easier, more secure logins.

Expert View

"Docker packages applications and their dependencies into containers, ensuring consistent environments across different systems. This isolation prevents resource conflicts and dependency issues." — techradar.com

→ See also: How to Host a Website on a Home Server?

FAQ

What hardware do I need for self-hosting as a beginner?

A mini PC, old desktop, NAS, Raspberry Pi, or dedicated server can serve as the host for a home lab. ([homeio.app](https://homeio.app/home-server-lab))

Is Docker too difficult for beginners to use?

While Docker introduces new concepts, its user-friendly tools and extensive documentation make it accessible to beginners.

How can I secure my self-hosted services from external threats?

Utilizing zero-trust mesh VPNs like Tailscale or Cloudflare Tunnels provides encrypted remote access to internal home lab dashboards without exposing home IP addresses directly to the internet. ([findtutu.com](https://findtutu.com/en/post/tech-homelab-self-hosting-docker-nas-guide-en/))

What are the most popular applications to self-host?

Services like Jellyfin, Immich, Pi-hole, Home Assistant, and Nextcloud are commonly self-hosted. ([homeio.app](https://homeio.app/home-server-lab))

Is it safe to expose my home lab to the internet?

Direct exposure of ports is risky. Always use VPNs (like Tailscale) or secure tunnels (like Cloudflare Tunnels) to access your services remotely. This greatly reduces your attack surface.

Can I move my home lab to new hardware?

Yes. As long as you have your Docker Compose files and data volumes backed up, you can reinstall Docker on new hardware, copy your files, and redeploy with minimal downtime.

What happens if I break my configuration?

If you use version control (like Git) for your Compose files and regular backups for your volumes, you can quickly roll back to a working state.

Do I need a static IP for my home lab?

No. Dynamic DNS services or VPN solutions like Tailscale make access reliable without a static IP.

Is self-hosting legal?

Personal self-hosting is almost always legal, but sharing services or hosting regulated data may have legal implications. Check local laws and compliance requirements.

Can I run more than one service on my hardware?

Yes! Docker was built for this. Use Docker Compose to manage multiple containers easily.

The Real Value of Self-Hosting in 2026

Self-hosting for beginners is not about chasing specs or impressing others with your hardware. It’s about owning your services, protecting your data, and learning skills that pay off well beyond your home lab. Every new container you run is one less dependency on someone else’s cloud. You’ll break things, sure, but you’ll also fix them—and that’s the point. The future of self-hosting is not reserved for experts. It’s for anyone who’s willing to start small, learn fast, and take back control—one container at a time.

Sources

1. techradar.com/pro/how-to-self-host-docker-apps
2. homeio.app/home-server-lab
3. selfhostedguides.com/docker-compose-self-hosting
4. findtutu.com/en/post/tech-homelab-self-hosting-docker-nas-guide-en