-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled error from config file #5
Comments
It seems that I've made a mistake when creating this project. To enable the blacklist or whitelist functionality the opentracker has to be build with modifications in the Therefore we must edit the
This will enable the whitelist functionality. If you want to use the blacklist approach, you have to use following:
Maybe I should restructure this project to use Also I should reference the original codebase from erdgeist.org as a BTW: I'm open for PRs ;) |
I use this in my docker-compose.yml
And the Dockerfile now looks like this:
I removed some of the whitespaces as docker would complain about them. p.s. I don't know much about the make process but I had to remove the space from |
Thank you for your contribution! 👍 The spaces were copy&paste errors, sorry for that. Fixed it in the original comment, too.
That woulf be great! |
Any idea why it outputs this
Unhandled line in config file: access.whitelist /etc/opentracker/whitelist.txt
when after editing the conf file?I've downloaded the git repo and uncommented the 37 line of the conf file
access.whitelist /etc/opentracker/whitelist.txt
.The image built without any issues but when I run it outputs that text. Container remains active, the file is present (checked with
exec -it <cont> sh
)The text was updated successfully, but these errors were encountered: