I already know incus supports Docker & LXC images as system images, incus probably supports running Docker application images but without managing them via compose files; (afaik)
Which is perfectly fine for incus as a fork of LXC with the main use case of running cloud-optimized linux system images, then you'd install & run service(s) just like bare-metal;
& also KVM support for non-native systems makes it viable for running non-linux workflows.
This makes it closer to Proxmox & VMware ESXi as they essentially do same thing using VMs.
Incus is just better in that regard. (OS-level containerization vs full-blown Linux VMs)
With incusOS, being immutable, relying on API / Web UI, supporting Kubernetes Cluster API (alpha?) & full disk encyption, it goes in the same tone as CoreOS &or MicroOS, which is more focused on running application images for workflows / services.
I know this sounds picky, but workflow doesn't really matter as long as deployment is satisfied;
I just want to know what IncusOS is trying to support, the images provided on the website emphasize the same system-image oriented workflow as LXC, Proxmox, just as Incus...
but some of the recent updates that came along IncusOS shows otherwise? I'm confused.
All I know is that CoreOS & MicroOS uses podman which support docker-compose as a plug-in,
Meaning you can use it to deploy Eg: Matrix server & all of it's deps as docker images pretty quickly.
On incus, you'd pull a debian system, install synapse, install a database, install a reverse proxy & configure synapse after these on the same linux container, which is more minimal & organized.
So, incusOS's gonna support both workflows in the future? Or bring it's own solution like Profiles?