Jump to content
Sign in to follow this  

linuxserver/unifi-controller - mongodb fails to setup socket

3 posts in this topic Last Reply

Recommended Posts



Anyone here running the unifi-controller on plain k8s? I'm trying it out in minikube on Ubuntu with a persistent hostPath volume.


First I had some trouble accessing the mounted volume but got it working by passing in the minkube vm docker user UID/GID as environmental variables in the pod, ie PGID=1000 and PUID=1000". Now I can connect to port 8443  and logs etc. are stored in the mounted directory. Seems as if everything ought to be correctly setup.


Now though the mongodb process don't have permissions to bind a socket for some reason.


2019-11-10T17:54:00.555+0000 E NETWORK  [initandlisten] listen(): bind() failed Operation not permitted for socket: /usr/lib/unifi/run/mongodb-27117.sock


If I enter the shell inside the pod both the unifi and mongodb processes run as user abc 911:911. I'm not sure how to interpret this in relation to the environment variables set, or why the mongodb process can't bind a socket. The unfi process can bind sockets (I guess?) as I can hit port 8443 and get a result back? 


Any help is appreciated.

Share this post

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this