From 08e6b1f6ed8442de17179bcb6572dfa7696dcb31 Mon Sep 17 00:00:00 2001 From: Ermanno Baschiera Date: Fri, 5 May 2023 22:52:40 +0200 Subject: [PATCH] avoid issues with timezone As reported here https://github.com/sdr-enthusiasts/docker-flightradar24/issues/116 and here https://github.com/sdr-enthusiasts/gitbook-adsb-guide/issues/101 this container needs to run on GMT timezone --- feeder-containers/feeding-flightradar24.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/feeder-containers/feeding-flightradar24.md b/feeder-containers/feeding-flightradar24.md index d6f0fad..89ca0e2 100644 --- a/feeder-containers/feeding-flightradar24.md +++ b/feeder-containers/feeding-flightradar24.md @@ -108,7 +108,6 @@ Append the following lines to the end of the file \(inside the `services:` secti - 8754:8754 environment: - BEASTHOST=readsb - - TZ=${FEEDER_TZ} - FR24KEY=${FR24_SHARING_KEY} tmpfs: - /var/log @@ -119,7 +118,6 @@ To explain what's going on in this addition: * We're creating a container called `fr24`, from the image `ghcr.io/sdr-enthusiasts/docker-flightradar24:latest`. * We're passing several environment variables to the container: * `BEASTHOST=readsb` to inform the feeder to get its ADSB data from the container `readsb` network. - * `TZ` will use the `FEEDER_TZ` variable from your `.env` file. * `FR24KEY` will use the `FR24_SHARING_KEY` variable from your `.env` file. * We're using `tmpfs` for volumes that have regular I/O. Any files stored in a `tmpfs` mount are temporarily stored outside the container's writable layer. This helps to reduce: * The size of the container, by not writing changes to the underlying container; and