<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<blockquote type="cite"
cite="mid:CA+3RNfik7FUNZZZGAMYzK6aprqcYpnk6Gjr5iD6brF_U2tL=2w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">There is also Ubuntu MicroCloud now, a new kid in
town. </div>
</blockquote>
<p>There is this discussion:
<a class="moz-txt-link-freetext" href="https://discuss.linuxcontainers.org/t/incus-vs-proxmox-vs-micro-cloud-feature-comparisons/23121/2">https://discuss.linuxcontainers.org/t/incus-vs-proxmox-vs-micro-cloud-feature-comparisons/23121/2</a></p>
<p>Some interesting notes/quotes/phrases:<br>
- arm64, no proxmox on it, yet; incus on Raspberry Pi cluster is
bueno<br>
- Proxmox requires a dedicated host</p>
<p>I'll say that I was forced into snaped ZFS to have newer LXD to
run vitual machines with microk8s. As was noted microk8s is a
distribution of k8s: can package kubes yourself, but easier is ...
easier. I wonder if IncusOS, with possibly future things around
rollouts in racks, will give Micro(Stuff) run for the money.
Competition is good.</p>
<blockquote type="cite"
cite="mid:CA+3RNfik7FUNZZZGAMYzK6aprqcYpnk6Gjr5iD6brF_U2tL=2w@mail.gmail.com">
<div class="gmail_quote gmail_quote_container">
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">>
What is the difference between an Incus and a Proxmox?<br>
<br>
Incus is LXC evolved, done right, not snap-ed (i.e.
Canonical's snap).<br>
<br>
They say Proxmox can use LXC to run systems not as virtual
machines.<br>
In time it'll be Incus, like TOFU with Terraform.<br>
<br>
From a user perspective, Proxmox has nice GUI and clicky
interfaces.<br>
In LXC, hence Incus, I ever used five-ish commands. And
similar will be<br>
with Incus. Add two more around migrating in upgrades. Proxmox
has<br>
some bunches of ready scripts to bring up things like CEPH
instances.<br>
Proxmox can be viewed as this higher level, with its own
decisions on<br>
that higher level, internally using five commands of lower
level, container<br>
and vm handler, if you allow this rhetorical stretch.<br>
<br>
Just found this <a
href="https://tadeubento.com/2024/replace-proxmox-with-incus-lxd/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://tadeubento.com/2024/replace-proxmox-with-incus-lxd/</a><br>
pointing that with addition GUI (in web) (finally), one may
start to use<br>
not only in terminal.<br>
<br>
Additionally, there is IncusOS <br>
<a href="https://stgraber.org/2025/11/07/introducing-incusos/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://stgraber.org/2025/11/07/introducing-incusos/</a><br>
which may be compared to Proxmox OS (?), and a whole OS setup
<br>
considerations.<br>
<br>
>>> We need a "+1" button for some of the emails on
this list.<br>
>> Paul, can count me in with Incus talk, for whenever
next year.<br>
>><br>
>> <a
href="https://linuxcontainers.org/incus/docs/main/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://linuxcontainers.org/incus/docs/main/</a><br>
>><br>
>> It'll be on admin-user level of Incus, similar to
what I did with LXC and<br>
>> Docker. Recent experience, bruises in
upgrade-in-recovery ... not<br>
>> recommended scheduling, has enough simple things to
share.<br>
>><br>
>>>> From recent experience:<br>
>>>><br>
>>>> If you trying to replace/attach/mess with
disks, and you insist, and you<br>
>>>> use -f for it, and ZFS still doesn't let you,
... , then just step away<br>
>>>> from the keyboard. Have some epistemic
humility towards yourself.<br>
>>>> Blindly taking out fdisk knife may increase
one's problems hundred-fold.<br>
>>>> Just step away, have coffee, reload the most
dynamic part of the system<br>
>>>> -- yourself.<br>
</blockquote>
</div>
</blockquote>
</body>
</html>