IncusOS seed config for migration-manager and operations-center?

IncusOS
, ,
1

It seems i am missing some important info on how to configure the additional applications on IncusOS.
I installed mm with incus admin os application add -d '{"name":"migration-manager"}'
In the logs i can see port 8443 is already occupied by the default incus application.
How would i set the listener address and port for example or how do i delete an application?

2

Oh, yeah, we should add some logic to prevent you from doing that :slight_smile:

@gibmat

Basically IncusOS can have one of three “primary” applications:

  • Incus
  • Migration Manager
  • Operations Center

Those should not be co-installable and only a single primary application should ever be allowed. Partly to avoid the port conflict issue but also because those applications are internally allowed to interact and reconfigure IncusOS, so you don’t want them to conflict with each other.

1 Like
3

Ah thats why, i thought i can define them on different ports on the same host in incusOS.
So basically i create an incusOS virtual machine in incus ( with the preseed config generator for example) and treat those as separate service instances?
Is that somewhere mentioned in the Docs that I should install either but not several applications on the same incusOS instance? I clearly missed that then
Thanks again for clear things up for me! :smiley:

Well
.and is there a way to remove those applications or do i need to reset incusOS and start fresh? :thinking:

4

We don’t currently have an API to uninstall applications and when we do, we won’t be allowing the removal of a primary application.

If this is a test system, reinstalling is probably easiest. If this is running inside of an Incus VM, we can provide instructions on manually removing the extra application.

Otherwise if it’s running on hardware and you can’t easily reinstall, it’s possible to manually clear the application by shutting down the system, booting it into a live Linux environment of some kind, then using cryptsetup access the root disk (requires the recovery key), mount it somewhere, then clear the extra application from /var/lib/extensions as well as from /var/lib/incus-os/state.txt before rebooting the system back into IncusOS.

5

I just reflashed the flash drive on which incusOS is running, thanks. Does incuOS puts settings in place if run from an external drive to minimize io and wear on such devices?

Anyway, if applications in incusOS are not really a modular thing, or not managable, then additional application installations should be prohibitid after the deployment of the application the user chooses.
It would be a nice feature to have simple applications managment (install/remove/delete/reset) in incusOS for isolated deployments on the same host with the option to set a listening address/port.

6

We have optional applications that are safe to add, things like debug, gpu-support, incus-ceph, incus-linstor.

It’s the three primary ones that are mutually exclusive as they each assume that they can interact with IncusOS and own the system.

7