unifi-docker/Dockerfile

78 lines
3.3 KiB
Docker

# FROM debian:jessie-slim
# WORKING: ends up being 500MB+
# FROM openjdk:8-jdk
# openjdk:8-jdk might sound like a good alternative, currently based on debian jessie, but Docker could switch that to apline some day? It's 600MB+!!
FROM debian:jessie-slim
# WORKING: work around openjdk issue which expects the man-page directory, failing to configure package if it doesn't
MAINTAINER Jacob Alberty <jacob.alberty@foundigital.com>
ARG DEBIAN_FRONTEND=noninteractive
ENV PKGURL=https://dl.ubnt.com/unifi/5.5.20/unifi_sysvinit_all.deb
# Need backports for openjdk-8
RUN echo "deb http://deb.debian.org/debian/ jessie-backports main" > /etc/apt/sources.list.d/10backports.list && \
echo "deb http://www.ubnt.com/downloads/unifi/debian unifi5 ubiquiti" > /etc/apt/sources.list.d/20ubiquiti.list && \
apt-key adv --keyserver keyserver.ubuntu.com --recv C0A52C50
# rather stick to what ubiquity themselves likely test with
#echo "deb http://downloads-distro.mongodb.org/repo/debian-sysvinit dist 10gen" > \
#/etc/apt/sources.list.d/21mongodb.list && \
#apt-key adv --keyserver keyserver.ubuntu.com --recv 7F0CEB10
# Push installing openjdk-8-jre first, so that the unifi package doesn't pull in openjdk-7-jre as a dependency? Else uncomment and just go with openjdk-7.
RUN mkdir -p /usr/share/man/man1/ && \
mkdir -p /var/cache/apt/archives/ && \
apt-get clean && \
apt-get update && \
apt-get install -qy --no-install-recommends curl gdebi-core && \
apt-get install -t jessie-backports -qy --no-install-recommends \
ca-certificates-java \
openjdk-8-jre-headless && \
curl -o ./unifi.deb ${PKGURL} && \
yes | gdebi ./unifi.deb && \
rm -f ./unifi.deb && \
apt-get purge -qy --auto-remove curl gdebi-core && \
apt-get clean -qy && \
rm -rf /var/lib/apt/lists/*
ENV BASEDIR=/usr/lib/unifi \
DATADIR=/var/lib/unifi \
RUNDIR=/var/run/unifi \
LOGDIR=/var/log/unifi \
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 \
JVM_MAX_HEAP_SIZE=1024M \
JVM_INIT_HEAP_SIZE=
RUN ln -s ${BASEDIR}/data ${DATADIR} && \
ln -s ${BASEDIR}/run ${RUNDIR} && \
ln -s ${BASEDIR}/logs ${LOGDIR}
# Can't use env var, RUN doesn't support them?
VOLUME ["${DATADIR}", "${RUNDIR}", "${LOGDIR}"]
# not sure if "/usr/lib/unifi/work" is needed as well?
#EXPOSE 6789/tcp 8080/tcp 8081/tcp 8443/tcp 8843/tcp 8880/tcp 3478/udp
EXPOSE 6789/tcp 8080/tcp 8443/tcp 8880/tcp 8843/tcp 3478/udp
## Uncommenting these allows unifi to run as user nobody but I don't know for sure that all features #work so leaving commented out for now
#RUN chown -R nobody:nogroup /usr/lib/unifi && \
# chown -R nobody:nogroup /var/lib/unifi && \
# chown -R nobody:nogroup /var/log/unifi && \
# chown -R nobody:nogroup /var/run/unifi
#USER nobody
COPY unifi.sh /usr/local/bin/
COPY import_cert.sh /usr/local/bin
RUN chmod +x /usr/local/bin/unifi.sh
RUN chmod +x /usr/local/bin/import_cert.sh
WORKDIR /var/lib/unifi
# execute controller using JSVC like original debian package does
CMD ["/usr/local/bin/unifi.sh"]
# execute the conroller directly without using the service
#ENTRYPOINT ["/usr/bin/java", "-Xmx${JVM_MAX_HEAP_SIZE}", "-jar", "/usr/lib/unifi/lib/ace.jar"]
# See issue #12 on github: probably want to consider how JSVC handled creating multiple processes, issuing the -stop instraction, etc. Not sure if the above ace.jar class gracefully handles TERM signals.
#CMD ["start"]