Tom Parrott

> > I've not looked at the code, but if these structs need to be accessible to the caller why are they being moved to internal and then interfaces being...

> > Can you define the types externally to `internal` and then use them from both the `/internal` functions and the call sites (like `shared.api`)? > > Yes that is...

> `/internal/sql` should not be on TLS listener (unix only). So important!

This seems expected, the container started ok, but then wasnt able to boot due to the process limit and stopped.

Yeah, its a bit tricky, because when a start operation is running LXD reports the container is running, so it only reports it as stopped once the start operation fails....

The "...ing" statuses isn't a new idea, see https://github.com/canonical/lxd/issues/10625 and has its own complexities. > I think it might be better to update the status of the instance at the...

``` DEBUG [2024-09-05T12:07:34+02:00] Start finished instance=u4 instanceType=container project=default stateful=false DEBUG [2024-09-05T12:07:34+02:00] Instance operation lock finished action=start err="Failed to run: /home/edlerd/go/bin/lxd forkstart u4 /var/lib/lxd/containers /var/log/lxd/u4/lxc.conf: exit status 1" instance=u4 project=default reusable=false...

But also this line is important: ``` DEBUG [2024-09-05T12:07:34+02:00] Instance initiated stop action=stop instance=u4 instanceType=container project=default ``` As originally thought, its the lxc instance itself which stops, not LXD asking...

> But also this line is important: > > ``` > DEBUG [2024-09-05T12:07:34+02:00] Instance initiated stop action=stop instance=u4 instanceType=container project=default > ``` > > As originally thought, its the lxc...

So somehow we need to resolve the conflict between the instance apparently failing to start: ``` ERROR [2024-09-05T12:07:34+02:00] Failed starting instance action=start created="2024-09-05 10:05:00.133727164 +0000 UTC" ephemeral=false instance=u4 instanceType=container project=default...