Issues with the gobgp_to_mongo.py file

[Suriiiiiii]

Hi,

After following the tutorial, we got the dashboard running. However, it is not being updated with new data.

The following errors keep popping up constantly when we run the build:

gobgp_1 | File "/var/tmp/gobgp_to_mongo.py", line 177, in
gobgp_1 | sys.exit(main())
gobgp_1 | File "/var/tmp/gobgp_to_mongo.py", line 167, in main
gobgp_1 | prefix_from_gobgp = build_json(get_update_entry(line))
gobgp_1 | File "/var/tmp/gobgp_to_mongo.py", line 75, in build_json
gobgp_1 | '_id': update_entry['nlri']['prefix'],
gobgp_1 | TypeError: 'NoneType' object is not subscriptable

[tldale]

Did you find a fix for this? When i hit my IP i get "Internal Server Error" So for me its completely broken :(

[tldale]

So i did a little googling. New to Docker as well so didn't help. I was able to get everything up and running without issue by doing the following:

Edit these files:
flask/Dockerfile
gobgp/Dockerfile

and add the following right above "RUN apt-get update"

RUN sed -i 's/security/old-releases/' /etc/apt/sources.list
RUN sed -i 's/archive/old-releases/' /etc/apt/sources.list

After i did that i killed the running containers and pruned docker. Then proceed to the last instruction again to build and run the containers.

[Suriiiiiii]

So i did a little googling. New to Docker as well so didn't help. I was able to get everything up and running without issue by doing the following:

Edit these files:
flask/Dockerfile
gobgp/Dockerfile

and add the following right above "RUN apt-get update"

RUN sed -i 's/security/old-releases/' /etc/apt/sources.list
RUN sed -i 's/archive/old-releases/' /etc/apt/sources.list

After i did that i killed the running containers and pruned docker. Then proceed to the last instruction again to build and run the containers.

Hi tldale,

Sorry for the late response, this project was pushed to the side since I could not find any resolution to the above.

I got the update issue fixed by using FROM ubuntu 18.04 in the Dockerfile but the error I have seems to be due to a null entry in the database table.