Stéphane Graber

Current state of things here is that the `events` API now allows for reacting to either background operation changes or more general container lifecycle events. This combined with the regular...

@avsdev-cw for the proxy not sending the address, we have support for the haproxy type headers (proxy protocol) whcih then does send you the address so long as your application...

@avsdev-cw you misunderstand what this feature is. There is no need for haproxy anywhere. You just set `proxy_protocol=true` on the proxy device and then in the container the target application...

Easiest may be a systemd unit like this one: ``` [Unit] BindsTo=sys-subsystem-net-devices-lxdbr0.device After=sys-subsystem-net-devices-lxdbr0.device systemd-resolved [Service] Type=oneshot ExecStartPre=/usr/bin/resolvectl dns lxdbr0 10.178.4.1 ExecStart=/usr/bin/resolvectl domain lxdbr0 '~lxd' [Install] WantedBy=sys-subsystem-net-devices-lxdbr0.device ``` Put that in...

Excellent, I'm sure it will be useful to some other folks!

Indeed. @tomponline want to update that part of the doc?

I think I responded to a similar question before. The conclusion was that I'd be happy to review a branch which either introduces a different return code in such case...

Indeed, we don't want to do string matching on things like that but could make better use of some HTTP codes to indicate that something is already in the desired...

I'm not sure there's a lot we can do about this. The reason is that: - There is no such thing as "initializing LXD", `lxd init` isn't special in any...

> Is there a reason why it _can't_ be special? There's nothing to stop lxd init --overwrite from deleting the database, is there? Since it's not an `lxc` command, it...