Replies: 1 comment 1 reply
-
If this fails it seems we don't correctly handle the case when the none is set in the config file so I would say this is a bug |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
According to docs
The special value “none” can be specified to disable creation of /etc/resolv.conf in the container.
Used the following file /home/user/test.conf:
Got:
Tried
dns_servers = none
,dns_servers =
which resulted in similar error; anddns_servers = ["none"]
which madenetavark
complain about wrong IP address format whilepasta
created the file withnameserver none
in it.With
--dns none
option got expected behavior:Tested on 4.9.3, 5.4.1, 5.5.1 and 5.6.0-dev (main, commit dbebcbe)
Any ideas on how to set containers.dns_servers to "none"?
Beta Was this translation helpful? Give feedback.
All reactions