Running Incus in a Proxmox Ubuntu 24.04 VM for a Private Cloud Homelab

If you want a more cloud-like way to run workloads in your homelab, Incus is worth paying attention to. The setup here is simple and practical. Run Incus inside an Ubuntu 24.04 virtual machine on Proxmox, then use Incus to manage full Linux systems through containers and virtual machines without turning your Proxmox host into a dumping ground for every experiment.

That is really the big appeal. You get another layer that is built for spinning things up, testing ideas, learning automation, and organizing services in a cleaner way.

What Incus brings to the table

The focus in this setup is not just basic virtualization. Incus is presented as a private cloud style environment for your own hardware. That means it is useful when you want something more structured than random VMs, but you are not trying to build some massive enterprise platform either.

The core capabilities highlighted are:

• Running containers
• Running virtual machines
• Taking snapshots
• Using profiles
• Supporting learning, testing, and automation
• Scaling workloads in a more organized way

That combination is what makes Incus interesting in a homelab. You can use it as a place to build real-world deployments while keeping your main virtualization environment from getting cluttered.

Why run it inside Proxmox instead of directly overloading Proxmox

A lot of homelab users already lean on Proxmox for everything. The problem is that once every test VM, every Linux experiment, and every temporary service lands there, it gets messy fast.

The approach here is to install Incus inside an Ubuntu 24.04 VM that lives on Proxmox. That gives you separation.

Proxmox stays the platform hosting your core virtual machine. Inside that VM, Incus becomes the environment where you create and manage the workloads you actually want to play with.

That is a smart homelab pattern for a few reasons:

Cleaner organization

You are not mixing every lab experiment directly into your main Proxmox view.

Better learning flow

If your goal is to understand containers, VM orchestration, snapshots, and reusable profiles, Incus gives you a focused platform to learn those concepts.

Easier testing

When you want to spin something up, break it, clone it, or snapshot it, having a dedicated layer for that work makes the whole process feel more intentional.

Who this setup is really for

This build is aimed at a few very specific types of users.

Homelab builders

If you have your own hardware and want to do more with it, Incus gives you another way to carve up resources and deploy Linux systems without immediately resorting to a full new Proxmox VM every time.

DevOps learners

If you are trying to learn infrastructure concepts in a hands-on way, this kind of environment is useful. Containers, virtual machines, snapshots, and profiles all map nicely to the kinds of operational ideas people need to understand in real environments.

Self-hosters

If you host your own services and want a secure environment to test or organize deployments, this setup gives you room to do that.

Linux beginners who want to go deeper

The video specifically frames this as approachable even if you are newer to Linux. That matters. You do not need a giant enterprise stack to start learning how modern workload management feels.

The installation path covered

The workflow is centered on Ubuntu 24.04 running as a VM on Proxmox. From there, the process moves through a pretty logical sequence.

1. Prepare the Ubuntu system and install Incus packages

The first step is updating the system and installing the packages needed for Incus.

That sounds basic, but it sets the tone for the whole build. Instead of treating Incus like some giant black box, the process starts with a clean Linux foundation inside the VM.

2. Initialize the Incus server

The next major step is initializing the Incus server with incus admin init.

This is one of the most important moments in the setup because it turns a basic package install into an actual usable Incus environment. Initialization is where the platform starts becoming your management layer instead of just software sitting on disk.

3. Launch your first container

After initialization, the next practical step is creating a container.

This is where the value of Incus becomes real. Instead of just talking about cloud-style management, you are now deploying a Linux system you can actually use.

4. Manage the container lifecycle

The workflow also includes basic container operations like:

• Stop
• Start
• Delete

Those are simple actions, but they matter because they are the daily mechanics of running lab workloads. If a platform is going to be useful, it has to make these routine tasks straightforward.

5. Create a virtual machine

Incus is not limited to containers here. The setup also demonstrates creating a VM.

That is one of the reasons Incus stands out in this context. It is not just a container tool. It can manage both containers and virtual machines, which makes it more flexible for homelab users who need different kinds of workloads.

Profiles are one of the most practical features

Profiles are called out as a dedicated topic, and that makes sense. In any environment where you plan to launch more than one workload, reusable configuration becomes a big deal.

Profiles help you avoid repetitive setup. Instead of handling every workload as a one-off snowflake, you can think in terms of standard patterns.

That is especially helpful for:

• Lab consistency
• Repeated testing
• Automation practice
• More predictable deployments

If you are trying to build real-world habits in your homelab, profiles are one of the features that push things in that direction.

Snapshots and clones make experimentation safer

Another big capability covered is snapshots and clones.

This is one of those things that instantly makes a homelab more useful. You are no longer stuck with an all-or-nothing approach to testing. You can create a state you trust, snapshot it, then experiment.

If something goes sideways, you have a recovery point.

Cloning adds another layer of convenience. Once you build something useful, you can duplicate it and branch off into new tests or service variations without starting over from scratch.

For learning environments, that is huge.

A concrete mistake to avoid

One of the main themes here is using Incus so you do not overload Proxmox. That is the gotcha to keep in mind.

A common mistake would be treating Proxmox as the place for every single lab task while also ignoring the structure that Incus gives you. If your goal is a secure, scalable, cloud-style environment for learning and testing, then dumping everything directly into Proxmox defeats the point.

The better approach is to let Proxmox host the Ubuntu 24.04 VM, then let Incus be the layer where you build, test, snapshot, and manage workloads.

That separation is not just cleaner. It is the whole reason this setup makes sense.

Resource planning matters

The video also touches on installation options and resource requirements. Since the focus stays high level, the key takeaway is simple: do not treat Incus like it has no footprint just because it is helping you organize workloads more efficiently.

You still need to think about the underlying VM and the hardware beneath it. Containers, VMs, snapshots, and clones all depend on the resources you assign and the capacity available in your homelab.

That does not mean you need a monster server. It just means planning matters.

Why this is useful for automation practice

Automation is specifically called out as one of the good use cases, and that fits naturally with what Incus offers.

When you can launch systems, manage them consistently, create profiles, and roll snapshots, you have a much better environment for repeatable work. That is the kind of setup that encourages better habits.

Even if you are not deep into DevOps yet, using a platform organized around these ideas can help you start thinking the right way.

The bigger takeaway

The interesting thing about this setup is that it is not trying to replace everything. It is not presented as a magical answer for every infrastructure problem. It is a practical way to get more out of your existing hardware and make your homelab more structured.

You keep Proxmox as your base virtualization platform.

You add an Ubuntu 24.04 VM.

Inside that VM, you run Incus as a private cloud style environment for containers, virtual machines, snapshots, profiles, and testing.

That gives you a platform that is useful for:

• Learning Linux and infrastructure concepts
• Building repeatable lab environments
• Testing without as much mess
• Practicing automation workflows
• Running both containers and VMs in one place

For a lot of people, that is the sweet spot. It is advanced enough to be powerful, but still approachable enough to use in a home lab without turning the whole thing into a full-time job.

Final thoughts

Incus looks like a strong option if you want a secure and scalable environment on your own hardware without making your Proxmox layer carry every experiment directly. The combination of containers, VMs, profiles, snapshots, and clones makes it especially appealing for learning and testing.

If you have been wanting a more private cloud feel in the homelab, this is a solid direction to explore.

Catch you in the next one.