OpenFortiVPN client container with static-route and NAT setup on Ubuntu 24.04.
1.2K
Ubuntu 24.04 (noble) container running a OpenFortiVPN client, with startup rules for static routes, packet forwarding and NAT. This is a VPN client, not a VPN server.
| Tag | Base | Published platform |
|---|---|---|
latest | ubuntu:noble | linux/amd64 |
Checked on 2026-11-08. The tag is updated in place; use a digest to pin an exact image. No native ARM64 variant is currently advertised.
/dev/ppp device.NET_ADMIN inside the container for interface, route and firewall operations.Place your configuration at ./default.conf. The container reads /opt/openfortivpn/default.conf. If it references other files, mount those files at the referenced paths as well.
services:
forti-gw:
image: softfour/openfortivpn-gw:latest
cap_add:
- NET_ADMIN
devices:
- /dev/ppp:/dev/ppp
sysctls:
net.ipv4.ip_forward: "1"
environment:
TZ: "UTC"
volumes:
- ./default.conf:/opt/openfortivpn/default.conf:ro
restart: unless-stopped
docker compose config --quiet
docker compose up -d
docker compose logs --tail=100 forti-gw
Create the configuration file before starting Compose and protect any credentials it contains. No application port is published by this example.
The current source starts openfortivpn -c /opt/openfortivpn/default.conf --insecure-ssl. Earlier overview examples used client.conf; mounting that path alone does not match this command.
The startup firewall rules refer to tun0, while OpenFortiVPN normally uses a PPP interface such as ppp0. Validate the actual interface and routing before using this image as a gateway. The interface is not configurable through an environment variable in the current entrypoint.
--insecure-ssl is currently hard-coded. Upstream defines it as allowing insecure TLS protocols/ciphers; this is not an option to disable certificate validation. Treat this as an explicit compatibility limitation and verify your gateway's TLS requirements before deployment. See the OpenFortiVPN manual.
| Variable | Default | Purpose |
|---|---|---|
TZ | UTC | Container time zone |
ROUTE_MAPS | Empty | Static routes as CIDR:GATEWAY, separated by commas, semicolons or spaces |
FIREWALL_SUBNETS | Empty | Source subnets used in the startup FORWARD acceptance rules; see limitations below |
Example values for a topology where the next hop is reachable through eth0:
environment:
TZ: "UTC"
ROUTE_MAPS: "10.10.0.0/16:192.168.1.1,172.16.0.0/12:192.168.1.1"
FIREWALL_SUBNETS: "192.168.1.0/24;192.168.2.0/24"
Replace these example networks and next hops with values reachable in your container network. ROUTE_MAPS adds routes via eth0; it does not add host routes or force all traffic through the VPN. Route-add failures are currently ignored by the entrypoint, so inspect the installed routes.
The entrypoint adds NEW-connection acceptance rules from eth0 to tun0, an ESTABLISHED/RELATED acceptance rule, and a general POSTROUTING MASQUERADE rule. An empty FIREWALL_SUBNETS value adds a general acceptance rule for that forwarding path.
FIREWALL_SUBNETS does not establish a default-deny firewall policy: the current entrypoint adds acceptance rules without explicitly dropping other sources. Do not rely on this variable alone as an access boundary. The NAT rule is not restricted to the tunnel interface. A fail-closed kill switch and tunnel health check are not implemented by this entrypoint.
Other containers can share this service's network namespace using network_mode: "service:forti-gw". That uses the VPN container's routes, but traffic generated in the shared namespace is not controlled by the FORWARD source-subnet rules. Publish any required application ports on the VPN service. Separate-network clients require explicit routes through the gateway and working IP forwarding; merely connecting two containers to a Docker network does not select the VPN as their default gateway.
docker compose logs --tail=100 forti-gw
docker compose exec -T forti-gw ip address
docker compose exec -T forti-gw ip route
docker compose exec -T forti-gw iptables -S FORWARD
docker compose exec -T forti-gw iptables -t nat -S POSTROUTING
Check device availability, capabilities, configuration paths, certificates, tunnel interface, DNS and the return route from the remote network. Container running status alone does not prove that the VPN is connected or that traffic is isolated. Validate permitted and denied traffic, reconnection and tunnel-loss behavior in your topology before production use.
Logs may contain network or authentication details; redact them before sharing. Keep VPN configuration and credentials outside the image, mount configuration read-only and never commit credentials to the source repository.
Record the image digest and back up the configuration before upgrading:
docker compose pull forti-gw
docker compose up -d forti-gw
Recheck tunnel and routing behavior after recreation. For rollback, set image to the previous softfour/openfortivpn-gw@sha256:... digest and recreate the service with the matching configuration.
Maintained by Softfour. For support, use your existing Softfour support channel and include the image tag, digest, platform and relevant logs with credentials removed.
The repository README is the source for this Docker Hub overview. Documentation updates do not change image contents. No versioned image changelog is currently published; record the digest before upgrading.
Based on Ubuntu packages and OpenFortiVPN. Third-party components retain their respective licenses. Contact Softfour for licensing information about image-specific files.
Content type
Image
Digest
sha256:5fafab79c…
Size
71 MB
Last updated
about 10 hours ago
docker pull softfour/openfortivpn-gw