Closed amateusz closed 4 years ago
@amateusz the build is failing. Could you take a look at it?
This is funny! It worked yesterday, but it seems that they (Maxmind) have phased-out GeoIP1 databases from their website. (legacy GeoLite1 points now toβ¦ GeoLite2 https://dev.maxmind.com/geoip/legacy/geolite/ β click β https://dev.maxmind.com/geoip/geoip2/geolite2/)
Mainline openvpn-monitor
seems to support GeoIP2 format already, so I'll try to update this project accordingly (Dockerfile really)
It had started as http
β https
, but then the company at the other end of the line have removed their v1 databases all together; then current openvpn-monitor
specified in Dockerfile
was not compatible with v2 db; then an act of configuring this new (1.0.0) version required further modifications of Dockerfile
.
Problem:
Now the only way to pass the configuration is upon build
or changing the file manually inside a volume (if I understand docker correctly), which is not ideal. Those docker run -e
envs would be welcome - see below β
Todo:
β fix confd
templates for openvpn-monitor 1.0.0
to parse them properly. More detail: 20009549a2109f2fad13f8bfabefd8790539bc15
β ~and also.. I can't remember.. idk. I'll be porting it to armhf
now btw.~ My current Dockerfile
builds on armhf
out-of-the-box (armbian Linux orangepi 4.14.84-sunxi armv7l GNU/Linux
and raspbian Linux pimate 4.14.90-v7+ armv7l
)
Thank you. Merged in https://github.com/ruimarinho/docker-openvpn-monitor/commit/161708f051321d820e66d85767e0e7893a405997. Can you take a look please?
Geolite database is only accessible through
https
nothttp
.Regarding the change: apparently I'm using this project, even though it seems a bit like a stub πΆ