I am not sure if this is the right place to ask this. Is it possible or is in plan or definitely out of scope to use incus-compose in order to spin up an environment where I have instances of a mix nature? like some OCI containers, some system containers and maybe some VM? The thing is that I look at the compose syntax and I find it intuitive, plus the incus-compose do stuff on the background that I would find real useful: the project scope, the dns daemon, etc.
It is not impossible. But I think there are better tools for that. incus-apply does the same as incus-compose but for LXC’s and VM’s.
Also there is a OpenTofu/Terrorform for incus terraform-provider-incus.
The open question is howto marry those tools without inviting the dragons 
I’ll happily extend incus-compose to support those tools, for example with hooks.
About ic-dns in the upcoming v1.4.0 release, you can use it with other tools or standalone without incus-compose, the same applies to ic-healthd since v1.2.0.
Thanks I didn’t know this tool, I’ll check it out!
I have tried this and I think it is great if you have a few environment that has to stay in a certain way, so the complexity of the HCL spec is worth it. My primary use case is to create environments for testing specific scenarios and then throw them away and the yaml format with the simplicity of the compose format was a real win.
I wrote “Terrorform” 
The compose spec has IMHO no way to spin up full systems, we would have to come up with something (like with cloud-init).
Just brainstorming: There could be a simple way to integrate cloud-init with incus-compose, for a developer this could be a great way to spin up an environment.
I have to say: I wanna keep ic lightweight and if there are other ways to archive the same I would prefer those.
that is perfectly understandable and a good goal for the tool. I understand that my use-case is maybe too specific so maybe a more specific tool is needed (maybe I’ll simply fork incus-compose as a start to see if it is actually what I am looking for).
Do not hesitate to contact me (on Github is my E-Mail) if you have questions, if the resulting patch is not too big I might merge it.