Pritunl as a Docker container
Config (env)
PRITUNL_DONT_WRITE_CONFIGif set,/etc/pritunl.confwill not be auto-written on container start.PRITUNL_DEBUGmust betrueorfalse- controls thedebugconfig key.PRITUNL_BIND_ADDRmust be a valid IP on the host - defaults to0.0.0.0- controls thebind_addrconfig key.PRITUNL_MONGODB_URIURI to mongodb instance, default is starting a local mongodb instance in the container and use that.
Usage
Just build it or pull it from jippi/pritunl. Run it something like this:
docker run \
-d \
--privileged \
-p 1194:1194/udp \
-p 1194:1194/tcp \
-p 80:80/tcp \
-p 443:443/tcp \
jippi/pritunlIf you have a mongodb somewhere you'd like to use for this rather than starting the built-in one you can
do so through the PRITUNL_MONGODB_URI env var like this:
docker run \
-d \
--privileged \
-e PRITUNL_MONGODB_URI=mongodb://some-mongo-host:27017/pritunl \
-p 1194:1194/udp \
-p 1194:1194/tcp \
-p 80:80/tcp \
-p 443:443/tcp \
jippi/pritunlExample production usage:
mkdir -p /gluster/docker0/pritunl/{mongodb,pritunl}
touch gluster/docker0/pritunl/pritunl.conf
docker run \
--name=pritunl \
--detach \
--privileged \
--network=host \
--restart=always \
-v /gluster/docker0/pritunl/mongodb:/var/lib/mongodb \
-v /gluster/docker0/pritunl/pritunl:/var/lib/pritunl \
-v /gluster/docker0/pritunl/pritunl.conf:/etc/pritunl.conf \
jippi/pritunlThen you can login to your pritunl web ui at https://docker-host-address
Username: pritunl Password: pritunl
I would suggest using docker data volume for persistent storage of pritunl data, something like this:
## create the data volume
docker run \
-v /var/lib/pritunl \
--name=pritunl-data busybox
## use the data volume when starting pritunl
docker run \
--name pritunl \
--privileged \
--volumes-from=pritunl-data \
-e PRITUNL_MONGODB_URI=mongodb://some-mongo-host:27017/pritunl \
-p 1194:1194/udp \
-p 1194:1194/tcp \
-p 80:80/tcp \
-p 443:443/tcp \
jippi/pritunlThen you're on your own, but take a look at http://pritunl.com or https://github.com/pritunl/pritunl
Based on johnae/pritunl