You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In latest-alpine, the Unifi server fails to start because the java executable cannot open libjli.so:
<docker-entrypoint> EXEC - su-exec unifi:unifi /usr/bin/java -Xmx1024M -Dunifi.datadir=/usr/lib/unifi/data -Dunifi.logdir=/usr/lib/unifi/logs -Dunifi.rundir=/usr/lib/unifi/run -Djava.awt.headless=true -Dfile.encoding=UTF-8 --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.time=ALL-UNNAMED --add-opens java.base/sun.security.util=ALL-UNNAMED --add-opens java.base/java.io=ALL-UNNAMED --add-opens java.rmi/sun.rmi.transport=ALL-UNNAMED -jar /usr/lib/unifi/lib/ace.jar start
Error loading shared library libjli.so: No such file or directory (needed by /usr/bin/java)
[various relocation errors for missing symbols]
It appears that the shared library search paths in the container are for the wrong version of OpenJDK. The contents of the musl ld path file in the image are:
In latest-alpine, the Unifi server fails to start because the java executable cannot open libjli.so:
It appears that the shared library search paths in the container are for the wrong version of OpenJDK. The contents of the musl ld path file in the image are:
The last three directories do not exist in the container because it uses OpenJDK 17.
I was able to get the container running by executing the following command within the container to fix the library paths:
System information:
The text was updated successfully, but these errors were encountered: