Docker setting for GEOIPUPDATE_FREQUENCY not working about geoipupdate

[horgh]

Does it happen when you use docker run? Could it be that compose is restarting the exited container?

[loganmarchione]

Ah you're right. When I run this...

docker run --rm -it --name geoipupdate\
  --env GEOIPUPDATE_ACCOUNT_ID=XXXXXX \
  --env GEOIPUPDATE_LICENSE_KEY=XXXXXXXXXXXXXXXX \
  --env 'GEOIPUPDATE_EDITION_IDS=GeoLite2-ASN GeoLite2-City GeoLite2-Country' \
  --volume geoipupdate_data:/usr/share/GeoIP \
  maxmindinc/geoipupdate

...it runs once and exits.

# STATE: Creating configuration file at /etc/GeoIP.conf
AccountID XXXXXX
LicenseKey XXXXXXXXXXXXXXXX
EditionIDs GeoLite2-ASN GeoLite2-City GeoLite2-Country
# STATE: Running geoipupdate

What is the correct restart policy to run this with docker-compose? I tested on-failure (without setting GEOIPUPDATE_FREQUENCY) and I get an exit code of zero.
Exited (0) 2 minutes ago

So I'm assuming if you're using docker-compose, you need to either:

• specify GEOIPUPDATE_FREQUENCY
  or
• use restart: on-failure

[horgh]

I'm not very familiar with compose, but it sounds like either of those options would be appropriate. I think it depends how you'd want to schedule the updates for your use case.

For the second option, presumably geoipupdate would never re-run until you restarted the compose application, unless there's another way to schedule it with compose. Kubernetes has the CronJob resource for example. I'm not sure if compose has something equivalent for controlling scheduling of containers itself.