-
Notifications
You must be signed in to change notification settings - Fork 471
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 Bookworm to integration-tests #902
base: master
Are you sure you want to change the base?
Conversation
A few results for the ticket. The new container image runs in podman without any problems. In docker the container terminates immediately. The old cent os image does not run on my local machine as well. It behaves in the same way as in the github pipeline (my tests). The container freezes without starting the services it contains (webserver/proxy). The images all contain more or less systemd/init. This is not really an architecture or a use case for containers. Starting multiple processes could also be done with the help of e.g. supervisord. The real reason why init/systemd is included is probably to check services via goss. This would certainly not be possible in standard containers. |
Checklist
make test-all
(UNIX) passes. CI will also test thisDescription of change
The current used images / Dockerfiles are EoL. Starting add a supported Debian Bookworm image.
I did a few tests. Since Debian Jessy the check for run level does not work anymore.