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

Supervisor is running as root #106

Closed
mmatczuk opened this issue May 29, 2020 · 7 comments
Closed

Supervisor is running as root #106

mmatczuk opened this issue May 29, 2020 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@mmatczuk
Copy link
Contributor

2020-05-29 14:21:05,586 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.

Maybe we should drop supervisor and define a pure pod?

@mmatczuk mmatczuk added the kind/bug Categorizes issue or PR as related to a bug. label May 29, 2020
@mmatczuk
Copy link
Contributor Author

Plus that!

2020-05-29 14:21:05,608 CRIT Server 'inet_http_server' running without any HTTP authentication checking

@dahankzter
Copy link
Contributor

Which one is this? Agent? Should we really prepopulate a token is that what you are saying?

@mmatczuk
Copy link
Contributor Author

mmatczuk commented Jun 1, 2020

This is scylla container and Supervisor complaining, I say we should split scylla container to different containers running in the same pod.

@dahankzter
Copy link
Contributor

Yes we should make it as pure "container" as possible.

@dahankzter
Copy link
Contributor

We can have the operator sidecar start scylla using scyllas cmdline only.

@mmatczuk mmatczuk added kind/feature Categorizes issue or PR as related to a new feature. and removed kind/feature Categorizes issue or PR as related to a new feature. labels Jun 2, 2020
@ezbz ezbz added kind/feature Categorizes issue or PR as related to a new feature. and removed kind/bug Categorizes issue or PR as related to a bug. labels Nov 2, 2020
@ezbz ezbz added the triage label Feb 23, 2021
@ezbz ezbz added this to the 1.x milestone Feb 23, 2021
@ezbz ezbz removed the triage label Feb 25, 2021
@tnozicka tnozicka removed this from the v1.x milestone May 27, 2021
@scylla-operator-bot
Copy link
Collaborator

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out

/lifecycle stale

1 similar comment
Copy link
Contributor

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out

/lifecycle stale

@scylla-operator-bot scylla-operator-bot bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 19, 2024
@tnozicka
Copy link
Member

covered in #1940

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants