mirror of
https://github.com/fosrl/olm.git
synced 2026-05-06 19:01:02 -05:00
[GH-ISSUE #95] Can't disable DNS override anymore #412
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/olm#412
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @asardaes on GitHub (Feb 13, 2026).
Original GitHub issue: https://github.com/fosrl/olm/issues/95
Describe the Bug
In version 1.4.2 (tagged but no GitHub release BTW) the DNS override is enabled by default, and I can't disable it with the config JSON nor with env vars.
Environment
Olm container v1.4.2
To Reproduce
Update to 1.4.2, create a JSON config with
"overrideDNS":falseand set the file's path in env varCONFIG_FILE.Expected Behavior
Respect settings from JSON config.
@oschwartz10612 commented on GitHub (Feb 13, 2026):
I think you can do --override-dns=false to disable it.
Thanks for alerting me to the failure of the release of 1.4.2 - that was
a mistake and I am publishing it now.
Also, we are moving to promoting the pangolin cli as the best way to run
a machine client. I think its better user experience. Try:
sudo pangolin up --id y6tzfk5zwiob505 --secret ******** --endpoint
https://app.pangolin.net --attach
@asardaes commented on GitHub (Feb 14, 2026):
Ok,
--override-dns=falseworks as expected with the pangolin CLI, but--holepunch=falsedoesn't. I imagine this issue is still valid though, but I don't know if you still foresee end users running Olm directly.@oschwartz10612 commented on GitHub (Feb 15, 2026):
Yeah actually --holepunch does not really work anymore and should be
removed. I will do that.
But yeah we are now going to try to drive users into the pangolin CLI
instead of olm I think which is designed closer to how we expect things
to be used. Olm has some old baggage from the before times :}
@github-actions[bot] commented on GitHub (Mar 2, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Mar 16, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.