Skip to content
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

Runsvdir downside #56

Open
xuoja-acc opened this issue Nov 24, 2020 · 1 comment
Open

Runsvdir downside #56

xuoja-acc opened this issue Nov 24, 2020 · 1 comment

Comments

@xuoja-acc
Copy link

xuoja-acc commented Nov 24, 2020

Hi,

The usage of runsvdir is usefull to being able to restore from a backup but prevent gracefull stop of his childs processes when you try to stop the container.

The docker stop command attempts to stop a running container first by sending a SIGTERM signal to the root process (PID 1) in the container.

If runsvdir receives a TERM signal, it exits with 0 immediately (https://www.unix.com/man-page/centos/8/runsvdir/)

The aftermath of this : you can't gracefully stop nexus when you do any of this actions , because every of this commands send SIGTERM to the root process(runsvdir) :

  • kubectl delete
  • kubectl scale statefulset --replicas=0
  • helm delete
  • docker stop

Best regards.

@cmoroianu1
Copy link
Contributor

Hi @ajoux-accor! Thanks for reporting the issue, we will investigate possible ways to fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants