I’m trying to get quassel-core running in an lxd container. Trying to run via systemd gives:
Jan 30 17:23:05 mimir systemd[1]: quasselcore.service: Service hold-off time over, scheduling restart.
Jan 30 17:23:05 mimir systemd[1]: quasselcore.service: Scheduled restart job, restart counter is at 5.
Jan 30 17:23:05 mimir systemd[1]: Stopped distributed IRC client using a central core component.
Jan 30 17:23:05 mimir systemd[1]: quasselcore.service: Start request repeated too quickly.
Jan 30 17:23:05 mimir systemd[1]: quasselcore.service: Failed with result ‘signal’.
Jan 30 17:23:05 mimir systemd[1]: Failed to start distributed IRC client using a central core component.
Trying to run manually:
root@mimir:~# quasselcore
Segmentation fault
Not sure where to look next. Any pointers? This is a fresh container with nothing else installed, but fully updated. Static IP has been set. Network works (can ping google, etc).
Oh, interesting, so it’s the apparmor profile for quassel which somehow doesn’t work well in containers.
Should be a one-line fix to the profile to allow this particular operation.
Assuming you’re installing quasselcore from the distribution, I’d recommend you file a bug there with the particular apparmor error and if you feel like it, try tweaking the profile under /etc/apparmor.d to allow this particular operation.