From my perspective, issue is resolved.
Tags: -1 moreinfo
Hello!
Seems the upstream PR was closed at https://github.com/lxc/lxc/pull/2758
Can you please confirm if this still affects MariaDB in Debian?
If you have suggestions of changed needed on the MariaDB packaging,
please file a Merge Request on Salsa as a proposal. Thanks!
htt
Hi Matthew!
Thank you for this workaround.
Feel free to add any comment to https://github.com/lxc/lxc/pull/2758 if
needed.
The following instructions (step 2) resolve the situation:
lxc (1:3.1.0+really3.0.3-6) unstable; urgency=medium
LXC 3 got some significant changes from LXC 2.
1. The configuration files use different variables. A userland script
lxc-update-config is available to update automatically
Excellent, thanks.
On 2019-02-14 10:51 a.m., Faustin Lammler wrote:
Control: forwarded -1 https://github.com/lxc/lxc/pull/2758
Matthew,
I able to reproduce this and I have the exact same error (mariadb log +
apparmor on host).
Your workaround is working but it seems that removing only these
Control: forwarded -1 https://github.com/lxc/lxc/pull/2758
Matthew,
I able to reproduce this and I have the exact same error (mariadb log +
apparmor on host).
Your workaround is working but it seems that removing only these 3 lines
is sufficient:
> ProtectSystem=full
> PrivateDevices=true
> Prote
Hello Faustin,
I am unfamiliar with how libvirt works, so I cannot say.
I have debian testing running on the hardware and inside the
container. Everything is from official repo. I can get mariadb to
start by messing around with the systemd startup script.
This may entirely be a an apparmor
Hi Matthew,
Thanks for your report!
I have no platform setup to test this so I have to install one but I am
not a LXC expert. Do you think this could be tested into a libvirt VM?
If I understand correctly, you have a Debian testing host and you are
running an LXC container with 10.3 mariadb versi
Package: mariadb-server-10.3
Version: 1:10.3.12-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Upgrade to latest mariadb package on debian testing; within lxc continer.
Previous package was working fine...
on the container
9 matches
Mail list logo