PRITUNL_DONT_WRITE_CONFIG if set, /etc/pritunl.conf will not be auto-written on container start.PRITUNL_DEBUG must be true or false - controls the debug config key.PRITUNL_BIND_ADDR must be a valid IP on the host - defaults to 0.0.0.0 - controls the bind_addr config key.PRITUNL_MONGODB_URI URI to mongodb instance.Basic Useage
docker run \
-d \
--privileged \
-e PRITUNL_MONGODB_URI=mongodb://user:password@some-mongo-host:27017/pritunl \
-p 1194:1194/udp \
-p 1194:1194/tcp \
-p 80:80/tcp \
-p 443:443/tcp \
docker.rouing.me/docker/pritunl
Example production usage:
mkdir -p /gluster/docker0/pritunl/pritunl
touch gluster/docker0/pritunl/pritunl.conf
docker run \
--name=pritunl \
--detach \
--privileged \
-e PRITUNL_MONGODB_URI=mongodb://user:password@some-mongo-host:27017/pritunl \
--network=host \
--restart=always \
-v /gluster/docker0/pritunl/pritunl:/var/lib/pritunl \
-v /gluster/docker0/pritunl/pritunl.conf:/etc/pritunl.conf \
docker.rouing.me/docker/pritunl
Then 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 \
docker.rouing.me/docker/pritunl
Then you're on your own, but take a look at http://pritunl.com or https://github.com/pritunl/pritunl
Based on jippi/pritunl
Content type
Image
Digest
Size
61.9 MB
Last updated
almost 8 years ago
docker pull rouing/pritunl