Closed kmanadkat closed 1 year ago
Thanks for the report.
IMHO, The immediate fix would be to have immuos layer use dscl
on MacOS. I don't get how service install ever worked on MacOS.
However, I wonder if we can get out of the user management business completely.
DynamicUser
(which is what I am doing in this experimental package)@padurean @mmeloni what do you think?
@dmacvicar AFAIK running immudb as a service in MacOS never worked. It was assumed no one runs production servers on MacOS, hence the feature is not really needed.
Your suggestions sound good for me, although for Windows we still need to define and decide the approach.
I agree with @dmacvicar & @padurean . We almost never use MacOS for production, it is most likely ubuntu or linux I guess. But we developers might want to setup development environment just like production so that we can consider potential issues might occur when deploying in cloud virtual machine.
It will be easy to fix. https://github.com/codenotary/immudb/tree/master/cmd/sservice is os/customizable .
fwiw, just added a service to Homebrew, so users can do:
brew install immudb
brew services start immudb
Homebrew
thanks a lot @ankane!
What happened I want to run immudb as a service on macOS 11.2.3, I am following official docs It is failing when I run
immudb service install
in terminal. Below is the log:As far as I understand it is trying to use linux command
groupadd
but that doesnot exists in mac due to security reasons.What you expected to happen It was expected to be installed without issues, it could perhaps use currently logged in user instead of trying to run
groupadd
How to reproduce it (as minimally and precisely as possible) Run
sudo immudb service install
in macOS after setting immudb path in.bashrc
or.zshrc
Environment