netceteragroup / rpi-ttn-gateway Goto Github PK

I suspect that most people would rather want to run the TTN container in daemon mode rather than interactive mode (-dt vs. -it). It would run in the background and not block the CLI but you won't see the log output that normally spills to the console.

docker logs <container-id> could make that visible again if necessary. Or docker attach <container-id>. Or docker exec -i <container-id> /bin/bash and then poke around the container.

The only mandatory config params for a TTN gateway are:

• reset pin
• gateway EUI
• region i.e. TTN server

We can either

• leave it as-is to (potentially) be future proof or (again potentially) support non-TTN backends OR
• dump everything not strictly required thereby slimming our code and documentation

I followed the instructions, but I'm getting the following error when starting the container:

INFO: [main] Starting the concentrator
ERROR: [main] failed to start the concentrator
/usr/bin/entry.sh: line 93: fg: job has terminated

Any hints on what I might be doing wrong?

The first user to pull the image already ran into this: #5.

Rather than documenting the manual way to extract-and-build the EUI we could also document the following command: cat /sys/class/net/eth0/address | awk -F\: '{print $1$2$3"fffe"$4$5$6}'.

Currently we're setting the EU server statically at https://github.com/netceteragroup/rpi-ttn-gateway/blob/master/Dockerfile#L35.

We should allow users to pick a region (not the actual hostname) based on their country as per:

router.eu.thethings.network # EU 433 and EU 863-870
router.us.thethings.network # US 902-928
router.cn.thethings.network # China 470-510 and 779-787
router.au.thethings.network # Australia 915-928 MHz

Reference: https://www.thethingsnetwork.org/forum/t/new-addresses-for-cloud-services-update-your-gateways/1813

Helpful: $TRAVIS_COMMIT_RANGE
https://github.com/facebook/react/blob/master/.travis.yml#L19
https://github.com/opencontainers/runtime-spec/blob/8831b203606aa74d2bf5274108816dde7629fa6f/.travis.yml#L16

In the docker file we use "FROM resin/rpi-raspbian" which uses the latest release of the rpi-raspbian image. This can introduce instability when the parent image has changed in the meantime. Similarly cloning the master version of a git-repo in the Dockerfile can lead to inconsistent behavior if no tag has been used. If the image is built at different points in time the resulting image can look different with every build.

This can be compared to a maven release which should not have dependencies to any unreleased version of other libraries.

In addition the image on dockerhub should get tagged not just with "latest" but with versions

Thanks to @marschall for the input.

Here some more reading about the topic:
https://medium.com/@mccode/the-misunderstood-docker-tag-latest-af3babfd6375
http://blog.benhall.me.uk/2015/01/dockerfile-latest-tag-anti-pattern/
http://container-solutions.com/docker-latest-confusion/

It is kind of irresponsible to not at least point out that the RPi password should be changed. Or these gateways will become easy targets for malware attacks

The TTN script generates log output (quite a bit) that is lost if you don't persist it manually. If the container runs in daemon mode (see #17) you might want to mount the host OS and pipe the output to a host OS file. Down side: might contribute to SD card corruption in the long run.