Script 'export-datasources-and-dashboards' crashes continuously

[myawnhc]

I feel this must be something in my environment since it isn't failing for others, but I did find a simple fix/workaround on the web that I'd like to apply.

In my environment, the dashboard won't come up, as the script export-datasources-and-dashboards constantly crashes and is respawned as shown in the log snippet below:

2019-09-03 22:44:33,496 INFO exited: export-datasources-and-dashboards (exit status 1; not expected)
2019-09-03 22:44:33,502 INFO spawned: 'export-datasources-and-dashboards' with pid 255
2019-09-03 22:44:34,505 INFO success: export-datasources-and-dashboards entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-09-03 22:44:44,361 INFO reaped unknown pid 276
2019-09-03 22:44:45,309 INFO reaped unknown pid 379
2019-09-03 22:44:45,309 INFO exited: export-datasources-and-dashboards (exit status 1; not expected)
2019-09-03 22:44:45,312 INFO spawned: 'export-datasources-and-dashboards' with pid 461
2019-09-03 22:44:46,317 INFO success: export-datasources-and-dashboards entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-09-03 22:44:56,213 INFO reaped unknown pid 482
2019-09-03 22:44:57,174 INFO exited: export-datasources-and-dashboards (exit status 1; not expected)
2019-09-03 22:44:57,174 INFO reaped unknown pid 586
2019-09-03 22:44:57,178 INFO spawned: 'export-datasources-and-dashboards' with pid 670
2019-09-03 22:44:58,181 INFO success: export-datasources-and-dashboards entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-09-03 22:45:08,049 INFO reaped unknown pid 691

If there is a known way to get this to stop happening on my system, I'm open to suggestions.

I found this same issue documented here:
kamon-io/docker-grafana-graphite#113

This can be fixed by editing the script /src/export-datasources-and-dashboards and adding a line "exit 0" at the end, so that it appears to exit cleanly. This then allows the dashboard to function normally.

I'd be happy to make this change and submit a pull request if this is a satisfactory workaround. If there is a better fix I can apply so it doesn't crash on my system, even better.