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

Launch failure when using Root #167

Closed
bevel-zgates opened this issue Feb 12, 2021 · 5 comments · Fixed by #214
Closed

Launch failure when using Root #167

bevel-zgates opened this issue Feb 12, 2021 · 5 comments · Fixed by #214
Assignees
Labels
bug Something isn't working
Milestone

Comments

@bevel-zgates
Copy link

Hey guys, ran into a failure when trying to launch as root within WSL (Postgres failed to launch...). Switching back to a non-priv user seems to have fixed the issue. I believe the issue comes from trying to launch the postgres as root and not running the service as a different user, here's what I get when trying to run it directly:

root@Zindows:~/.steampipe/db/12.1.0/postgres/bin# ./postgres
"root" execution of the PostgreSQL server is not permitted.
The server must be started under an unprivileged user ID to prevent
possible system security compromise.  See the documentation for
more information on how to properly start the server.
@e-gineer e-gineer added the bug Something isn't working label Feb 12, 2021
@e-gineer
Copy link
Contributor

Thanks @bevel-zgates for reporting this! Hadn't occurred to us to try installing as root

Interesting problem ... I guess we could:

  1. Install a new user for running the postgres service. (We run embedded, so don't currently create a new user for it.)
  2. Refuse to install steampipe as root.

I think 2 is probably best?

@bevel-zgates
Copy link
Author

bevel-zgates commented Feb 13, 2021 via email

@kaidaguerre
Copy link
Contributor

Hey @bevel-zgates thanks a lot for the report.

 it just seemed most straightforward to me when I was dropping it into a container.

I'd be really interested to understand your use case here - I wonder if you could expand this a little?

Thanks!
kai

@bevel-zgates
Copy link
Author

bevel-zgates commented Feb 16, 2021 via email

@kaidaguerre
Copy link
Contributor

@bevel-zgates thanks for the details - it's really useful and interesting to see how people use the tool.

@kaidaguerre kaidaguerre added this to the 0.2.2 milestone Feb 22, 2021
@binaek binaek linked a pull request Feb 22, 2021 that will close this issue
ahirreddy pushed a commit to ahirreddy/steampipe that referenced this issue Jul 8, 2024
…d update azure-sdk to v55.4.0+incompatible closes turbot#167 (turbot#166)

* Add table azure_compute_disk_metric_read_ops closes turbot#161
* Add table azure_compute_disk_metric_read_ops_daily closes turbot#148
* Add table azure_compute_disk_metric_read_ops_hourly closes turbot#162
* Add table azure_compute_disk_metric_write_ops closes turbot#164
* Add table azure_compute_disk_metric_write_ops_daily closes turbot#149
* Add table azure_compute_disk_metric_write_ops_hourly closes turbot#165
* Add table azure_compute_virtual_machine_metric_cpu_utilization closes turbot#159
* Add table azure_compute_virtual_machine_metric_cpu_utilization_daily closes turbot#147
* Add table azure_compute_virtual_machine_metric_cpu_utilization_hourly closes turbot#160
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

Successfully merging a pull request may close this issue.

4 participants