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

tini should be used with -s argument #227

Open
orfeas-k opened this issue Jul 25, 2024 · 2 comments
Open

tini should be used with -s argument #227

orfeas-k opened this issue Jul 25, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@orfeas-k
Copy link
Contributor

Bug Description

Due to charms having pebble as PID 1, we should deviate from upstream and use tini with -s as instructed in the docs and also in the warning we get, when using it without:

2024-07-24T07:38:24.073Z [kubeflow-dashboard] [WARN  tini (15)] Tini is not running as PID 1 and isn't registered as a child subreaper.
2024-07-24T07:38:24.074Z [kubeflow-dashboard] Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
2024-07-24T07:38:24.074Z [kubeflow-dashboard] To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.

Thus th ecommand will be:

self._service = "/sbin/tini -s -- npm start"

To Reproduce

N/A

Environment

N/a

Relevant Log Output

n/a

Additional Context

No response

@orfeas-k orfeas-k added the bug Something isn't working label Jul 25, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-6050.

This message was autogenerated

@orfeas-k
Copy link
Contributor Author

orfeas-k commented Aug 1, 2024

From our discussion with rockcraft, it turns out that since we have pebble, we don't need to use tini. Thus, instead of adding an -s argument, we can just remove altogether.

Thus, we need to:

  1. Remove relevant comment (in main and track 1.9).
  2. Add context somewhere appropriate. Contributing.md file was suggested during the bug triage meeting but I don't think it's an appropriate place after all for adding an implementation detail. Modifying the comment above (next to the command) to link to this issue's comment could provide enought context too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant