[lxc-users] lxc config preventing mysql

Andrey Repin anrdaemon at yandex.ru
Mon Aug 21 13:46:16 UTC 2017


Greetings, Jake Black!

> So in our environment, we use lxc containers for quick test machines. We
> have a script that will spin up a container and set lxc config based on what
> we need it to do. We are running into an issue where these config settings are preventing mysql from starting.

> This is how the container is created if we need to mount nfs to it.

> lxc launch "${IMAGE}" "${NAME}"
> lxc config set ${NAME} security.privileged true
> lxc config set ${NAME} raw.apparmor 'mount,'

Why not just mount the necessary structure using LXD config?

> The specific mysql error being reported by ansible is invoke-rc.d:
> initscript mysql, action \"start\" failed.

Why "invoke-rc.d" ? What is the guest OS?

> Now if I just launch the container without the two config lines then when I
> run an ansible playbook that calls and sets up mysql, there is no mysql
> error and it actually started without error. So I tested to see which one of
> these lines was causing mysql to throw a fit. But it appears to be when both
> of these configs are set. If I just run one config line (doesn't matter
> which) then there is no error. The error only appears when both of these are ran.

> We initially did not suspect lxc configs to be messing with mysql. But
> found this by setting up identical containers and doing the same tasks
> except for these lines. And our playbooks that start mysql don't need nfs so
> we aren't really blocking on this, but is an interesting issue. Does anybody
> have any idea why these would be preventing mysql from starting?


-- 
With best regards,
Andrey Repin
Monday, August 21, 2017 16:44:23

Sorry for my terrible english...



More information about the lxc-users mailing list