Skip to content
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

flag provided but not defined: -svc-service-host #4

Open
vavallee opened this issue Oct 10, 2023 · 6 comments
Open

flag provided but not defined: -svc-service-host #4

vavallee opened this issue Oct 10, 2023 · 6 comments
Labels
question Further information is requested

Comments

@vavallee
Copy link

When I run the image, I get

flag provided but not defined: -svc-service-host

That value was auto-populated with the internal IP of my kubernetes pod.

@JeDaYoshi
Copy link
Owner

Likely because NEXTDNS_SVC_SERVICE_HOST is being defined as an environment variable, and the client is not going to recognise this. You need to make sure this is not passed to the container.

@JeDaYoshi JeDaYoshi added the question Further information is requested label Oct 10, 2023
@vavallee
Copy link
Author

vavallee commented Oct 10, 2023

ok. I tried defining that key and setting the value to "". But same results, here's the edited output.

Running with arguments: -setup-router=true -profile=11111111 -svc-service-host= -svc-port-5353-udp-addr=10.43.89.130 -svc-port-5353-udp-port=5353 -svc-port-5353-udp-proto=udp -use-hosts=false -svc-port=udp://10.43.89.130:5353 -svc-service-port=5353 -svc-port-5353-udp=udp://10.43.89.130:5353 -cache-size=10m -report-client-info=true -profile=11:11:11:11:11=config1 -svc-service-port-nextdns=5353 -profile=22:22:22:22:=config1

@JeDaYoshi
Copy link
Owner

Setting the value to "" will not work, they should be undefined entirely. Same with svc-port, svc-service-port etc. And like I said in the other issue, NAT will bring issues if you want MAC addresses to work.

@vavallee
Copy link
Author

ok, Since I am not defining these key/values, how can I remove them? My config is:

spec:
      containers:
      - env:
        - name: NEXTDNS_PROFILE
          value: "111111"
        - name: NEXTDNS_PROFILE_MYMAC
          value: 11:11:11:11:11=config1
        - name: NEXTDNS_PROFILE_ANOTHERMAC
          value: 22:22:22:22:22=config1
        - name: NEXTDNS_CACHE_SIZE
          value: 10m
        - name: NEXTDNS_REPORT_CLIENT_INFO
          value: "true"

@JeDaYoshi
Copy link
Owner

Can you try renaming the container to something else other than nextdns? First idea that comes to mind that wouldn't involve too much work.

@vavallee
Copy link
Author

It's actually called nextdns-filter in my kubernetes configs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants