-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Debian 11 and Ubuntu 22.04; drop EoL Ubuntu 18.04 and CentOS 8 #134
base: master
Are you sure you want to change the base?
Conversation
No idea why this is happening on the Debian 11 acceptance test:
It must be something about the docker container created by beaker, because chronyd runs fine on a real machine, and this specific pidfile error doesn't happen when running chronyd in a container of the debian:11 image from dockerhub. |
4a3f9bb
to
f50899e
Compare
Maybe not entirely related to beaker: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2004525 |
@rvm-peercode thanks for the link. I don't think that's the problem here though because these tests run in docker containers, so there is no apparmor involved, especially because apparmor is not enabled by default on Debian. Or it could be that https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2004525 actually isn't caused by apparmor. |
No description provided.