On 6/24/23 22:19, Mathias Gibbens wrote:
>> systemd-hostnamed.service is probably also affected, but in my case I
>> paved over the issue by setting PrivateNetwork=no in an override.
>
> For the moment setting PrivateNetwork=no for affected services is
> probably a better approach than totally
Control: tags -1 + confirmed
Control: forwarded
https://discuss.linuxcontainers.org/t/systemd-hostnamed-unable-to-start-on-lxd-5-0-containers/17454
Hi Bagas, Michael,
At first glance, this looks like an apparmor problem. Unfortunately
all the issues that have been mentioned previously are
Package: lxd
Version: 5.0.2-5
Followup-For: Bug #1038315
I'm unsure if current breakage is due to apparmor itself (the bug reported
there was apparently fixed a while ago), lxd's apparmor profile, or
somewhere else (as satisfying as blaming systemd would be...). See linked
bugs listed below.
Is
Package: lxd
Version: 5.0.2-5
Severity: important
Dear Maintainer,
I spin up containers using LXD. I'm primarily doing this for learning
purposes (for example installing and configuring web services).
I launched my first container (test) to get my feet wet by:
```
lxc launch images:debian/12
4 matches
Mail list logo
