https://github.com/boredazfcuk/docker-geoipdb
An Alpine Linux Docker container for creating a legacy GeoIP Database using sherpya's geolite2legacy conversion utility cusomised for use by my stack, Steve
https://github.com/boredazfcuk/docker-geoipdb
Last synced: 3 months ago
JSON representation
An Alpine Linux Docker container for creating a legacy GeoIP Database using sherpya's geolite2legacy conversion utility cusomised for use by my stack, Steve
- Host: GitHub
- URL: https://github.com/boredazfcuk/docker-geoipdb
- Owner: boredazfcuk
- Created: 2019-09-10T23:50:05.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2024-10-15T13:32:53.000Z (12 months ago)
- Last Synced: 2025-07-02T11:52:59.867Z (3 months ago)
- Language: Shell
- Homepage:
- Size: 18.6 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: change.log
Awesome Lists containing this project
README
# docker-geoipdb
An Alpine Linux Docker container for creating a legacy GeoIP Database using sherpya's geolite2legacy conversion utility
## VOLUME CONFIGURATION
This container requires a single volume. This can either be a named volume, or a bind mount to the host's GeoIP Database directory (/usr/share/GeoIP on my system).
## CREATING A CONTAINER
To create a container, run the following command from a shell on the host, filling in the details as per your requirements:
```
docker create \
--name \
--hostname \
--network \
--env TZ= \
--volume : \
boredazfcuk/geoipdb
```
As an example, this is the actual command I run on my host to create the container:
```
docker create \
--name=GeoIPDb \
--hostname geoipdb \
--network containers \
--restart always \
--cpus 1 \
--env TZ=Europe/London \
--volume geoipdb_data:/usr/share/GeoIP/ \
boredazfcuk/geoipdb
```
When this container first starts up, it will create and folders it needs and display the variables it's using. It will also create a crontab entry to run the database update function between 4-5am on Thursday mornings. I have randomised the minute so different installs will connect to the upstream servers at different times. Also, Maxmind release weekly updates to their database every Wednesday, so there's no point checking on other days.
When this container performs an update, it will hog CPU resources as is is very processor intensive. As it's not a critical service, I have limited it to only using a single CPU core so it doesn't interfere with more important stuff.
I also set the restart option to 'always' so that the container will automatically start up after host reboots.
Litecoin: LfmogjcqJXHnvqGLTYri5M8BofqqXQttk4