Hello, Le sam. 12 oct. 2019 à 01:26, Jose-Luis Rivas <ghost...@debian.org> a écrit : > > Hello Scott, > > On 10/11/19 18:49, Scott Kitterman wrote: [...] > In short: they should not be using systemd inside the container and if > they want to the issue is not on how Debian ships systemd but that they > are not using the --privilege parameter for launching their container.
While I agree to not recommend using systemd inside docker, it is very useful in CI. We use this at work to test our salt states (salt is like puppet/ansible/chef/...). For this, we use Gitlab CI running test-kitchen with ruby-kitchen-salt and ruby-kitchen-docker (all in buster). Another solution would either mean hacking gitlab-runner [1] or spanning a lot of VMs. [1]: https://gitlab.com/gitlab-org/gitlab-runner/issues/1585 Also systemd can be run inside Docker without --privileged but requires careful configuration [2]. [2]: https://developers.redhat.com/blog/2016/09/13/running-systemd-in-a-non-privileged-container/ Regards -- Mathieu Parent Parent