Right now this requires some manual steps:
- reading the docker file to understand what kind of instances are created
- now create each instance the same way on incus
The tedious part is adding all required env variables and adding persistent storage volumes.
After this has been deployed successful updating each OCI container is pretty much straight forward. This approach comes with another advantage where you can reuse things like databases or redis with multiple stacks to save resources but adds more dependencies.
OCI support is still in early stages and projects like Incus-Compose will make it simpler to deploy. For now it is rather manually but all do able.
In regarding to S6 I haven’t had any issues with recent Incus releases. In case you need to add some additional steps I think you can add (mount) a custom script. Take a look at this thread Incus proxy bind to host address issue - #9 by osch to get ideas what is now possible to avoid tinkering with OCI init scripts.