Hi Mathias (2024.02.18_19:43:13_+0000) > I suspect you're seeing this on the host system running Incus? If so, > that's expected behavior.
Nope, in a VM inside Incus. > Incus' default mode of operation when launching a VM is to > dynamically inject the `incus-agent` binary into the VM's environment. It does that if incus-agent-setup is in the image. This was an image without incus-agent-setup, just your incus-agent package. If the intention isn't to use the incus-agent package inside VMs, this should be declared more clearly. > This setup covers the vast majority of regular Incus use. But, > because there is an incus-agent package we also need to support someone > creating a VM image that bakes in that package. Thus, there's a service > definition in the incus-agent package. The ConditionPathExists check > should ever only be true within a VM running under Incus. That's was my use-case here, and it doesn't work, due to a race. I've convinced myself that this isn't really the best way to go. And instead of installing incus-agent in my images, I need the incus-agent-setup unit that installs the agent over 9p. Getting incus-agent from the host is likely to be much more reliable, because the Incus upstream isn't expecting to have to support ancient agents. > I've just verified that both use cases appear to work properly, so > I've downgraded the bug's severity to normal. Use a bare image without incus-agent-setup to reproduce the bug. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
