Unifi controller how to set up
-
- OMV 4.x
- skank
-
-
/config is a container path, not a host path and it must point to a host directory not left blank. Also it probably will not work if set read only (R/O).
-
/config is a container path, not a host path and it must point to a host directory not left blank. Also it probably will not work if set read only (R/O).
i have to create a path first, or doest it autocreate when i fill something in
something like /Appdata/Unifi
edit: filled something in, and got rid of the read only.
Still no gui, should it be an extra button to go to gui? or do i doubleclick or? -
-
i did
when i ente ip:8443 i get error
however in the container i dont see a port filled innor do i see a place where i can fill in
Questions remains if its active, will i see something like "web gui" to click on or?
-
When you select Host networking you don't have to specify any ports. But this does not mean it is guaranteed to work. It's possible to have port conflicts with other applications.
The OMV Docker WebGUI does not provide buttons to access applications.
Read the container log for hints.
-
its the first docker running so no conflicts i think
the log says
standard_init_linux.go:211: exec user process caused "exec format error" -
its the first docker running so no conflicts i think
the log says
standard_init_linux.go:211: exec user process caused "exec format error""exec format error" means you are running an image meant for one system architecture on a different system architecture.
In other words if you are running a linux/amd64 docker image on hardware that isn't Intel x86 or AMD64 then it will not work.
What image are you running and on what hardware?
-
https://hub.docker.com/r/linuxserver/unifi
on a raspberry pi 3b+
Then why does this show up, when its not compatible
-
That is a linux/amd64 image and it will not run on your hardware. There is nothing in the OMV Docker WebGUI to prevent loading inappropriate images.
You need to find an armhf image somewhere. Google for it.
-
ok thx
-
Then why does this show up, when its not compatible
Depends on where it "showed up".Most likely it showed up because the software you used just matched a search term you typed in, without applying advanced AI natural language techniques to read and interpret the documentation to determine compatibility. It would be great with software selection tools with AI compatibility determination. I fear it still is a few years into the future. Until then:
It is a good idea to read the documentation before installing anything. For instance the docker tags, to verify compatibility.
-
Found this one
https://hub.docker.com/r/linuxserver/unifi-controllerLukt nog niet , maar wel al verder volgens mij
Logs zeggen
s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------User uid: 911
User gid: 911
-------------------------------------[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /config/data/keystore -destkeystore /config/data/keystore -deststoretype pkcs12".
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
OpenJDK Client VM warning: You have loaded library /usr/lib/unifi/lib/native/Linux/armv7/libubnt_webrtc_jni.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'. -
En nu is hij wel bereikbaar
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!