zygmunt

Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

zygmunt's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Ooh, I thought he referred to the application support forums. Just found out linuxserver.io has forums to. Thanks!
  2. Hi, 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.
  3. I'm trying to run the image in k8s but can't get it to work with permanent storage. As long as I don't define a persistent volume it works as intended. When I define a hostpath volume for the /config directory the controller process refuses all connections. The pod creates three directories in the mounted hostvolume: data, logs and run. The data directory contains a binary file named keystore, the others are empty. Inside the pod there's a java process running using the user abc 911:911 and command, java -Xmx1024M -jar /usr/lib/unifi/lib/ace.jar The unifi service is not running. No sign of any mongodb process or service. I'm not sure how to troubleshoot this. Any pointers are appreciated. It's obviously related to the storage.