[OSGeo] #2894: Update of grass.osgeo.org to Debian 11
OSGeo
trac_osgeo at osgeo.org
Tue Sep 3 07:28:16 PDT 2024
#2894: Update of grass.osgeo.org to Debian 11
----------------------+---------------------------------------
Reporter: neteler | Owner: sac@…
Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2023-I
Component: SysAdmin | Resolution: fixed
Keywords: debian |
----------------------+---------------------------------------
Comment (by robe):
Replying to [comment:12 lnicola]:
> I don't think we should be disabling systemd-logind, that will probably
break D-Bus user sessions. If SSH is slow to log in, that's probably
https://github.com/systemd/systemd/issues/17866.
>
> I didn't look too closely, but it looks like a bad LXC/AppArmor
interaction that was fixed in bookworm in 2021: https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=995350).
>
> Instead, I fixed it by setting `security.nested=true` on the container.
Apparently this is fine for unprivileged containers, but we should check
using `lxc list security.privileged=true` beforehand.
>
> Of course, my preference would be to upgrade to a distro that has proper
support.
>
> PS: we also ran into an `acpid` issue (it was using a lot of CPU), `apt
purge acpi-support` fixes that. Again, that might have been fixed, but a
container doesn't need ACPI anyway.
Thanks that did seem to fix the issue and the logrotate failing:
{{{
lxc config set grass security.nesting=true
lxc exec grass -- systemctl unmask systemd-logind.service
}}}
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2894#comment:13>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
More information about the Sac
mailing list