This Docker image contains an openconnect client (version 8.04 with pulse/juniper support) and the squid proxy server for http/https connections.
If you don't want to set the environment variables on the command line
set the environment variables in a .env
file:
OPENCONNECT_URL=<Gateway URL>
OPENCONNECT_USER=<Username>
OPENCONNECT_PASSWORD=<Password>
OPENCONNECT_OPTIONS=--authgroup <VPN Group> \
--servercert <VPN Server Certificate> --protocol=<Protocol> \
--reconnect-timeout 86400
Don't use quotes around the values!
See the openconnect documentation for available options.
Either set the password in the .env
file or leave the variable OPENCONNECT_PASSWORD
unset, so you get prompted when starting up the container.
Optionally set a multi factor authentication code:
OPENCONNECT_MFA_CODE=<Multi factor authentication code>
To start the container in foreground run:
docker run -it --rm --privileged --env-file=.env \
-p 3306:3306 -p 8889:8889 alimaster/openconnect-squid-proxy:latest
The proxies are listening on ports 3306 (http/https). Either use --net host
or -p <local port>:3306 -p <local port>:8889
to make the proxy ports available on the host.
Without using a .env
file set the environment variables on the command line with the docker run option -e
:
docker run … -e OPENCONNECT_URL=vpn.gateway.com/example \
-e OPENCONNECT_OPTIONS='<Openconnect Options>' \
-e OPENCONNECT_USER=<Username> …
To start the container in daemon mode (background) set the -d
option:
docker run -d -it --rm …
In daemon mode you can view the stderr log with docker logs
:
docker logs `docker ps | grep "alimaster/openconnect-squid-proxy" | awk -F' ' '{print $1}'`
version: '3.2'
services:
vpn:
container_name: vpn
image: alimaster/openconnect-squid-proxy:latest
ports:
- 0.0.0.0:3306:3306
privileged: true
env_file:
- .env
cap_add:
- NET_ADMIN
Set the environment variables for openconnect in the .env
file again (or specify another file) and
map the configured ports in the container to your local ports if you want to access the VPN
on the host too when running your containers. Otherwise only the docker containers in the same
network have access to the proxy ports.
Let's say you have a vpn
container defined as above, then add network_mode
option to your other containers:
depends_on:
- vpn
network_mode: "service:vpn"
Keep in mind that networks
, extra_hosts
, etc. and network_mode
are mutually exclusive!
The container is connected via openconnect and now you can configure your browser and other software to use one of the proxies (3306 for http/https).
For example FoxyProxy (available for Firefox, Chrome) is a suitable browser extension.
You may also set environment variables:
export http_proxy="http://127.0.0.1:3306/"
export https_proxy="http://127.0.0.1:3306/"
composer, git (if you don't use the git+ssh protocol, see below) and others use these.
You can build the container yourself with
docker build -f build/Dockerfile -t alimaster/openconnect-squid-proxy:custom ./build