mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 09:25:56 +03:00
[GH-ISSUE #586] Bug: current machine does not support all of the following #194
Labels
No labels
bug
confirmed
discussion
duplicate
enhancement
feature
feature-request
not-planned
pull-request
secondary-feature
stale
triage
waiting-feedback
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/dns-proxy-server-mageddo#194
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @SiriosDev on GitHub (Oct 7, 2024).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/586
What is Happening
Using the following compose (derived from the run recommended in the docs) the container does not start giving in the logs only the lack of some instruction sets (read the logs below)
the processor is an Intel(R) Celeron(R) J4125 CPU, so fairly recent, also I didn't put the suffix for arch
What is Expected
Describe what you expected to happen.
Specs
27.3.1latest(cant run)@julipercas commented on GitHub (Oct 21, 2024):
I'm also having this problem only since recently, even though I've been using dps-dns in docker for months without issues.
@mageddo commented on GitHub (Oct 21, 2024):
Looks like it's related to build optimizations, [1] [2]
Can you confirm that version
3.26.0-snapshotworks great and3.29.0-snapshotdon´t?@SiriosDev commented on GitHub (Oct 21, 2024):
I've tried
3.243.26latestnightlyand3.30.2, all same error@mageddo commented on GitHub (Oct 21, 2024):
Made an adjustment, releasing
3.30.4-snapshotright now, try check it out later.@SiriosDev commented on GitHub (Oct 21, 2024):
Yep now work, in this moment u r the savior of my self host mental sanity
@mageddo commented on GitHub (Oct 22, 2024):
Glad to help :)
@SiriosDev commented on GitHub (Oct 22, 2024):
For my needs it works perfectly, but I discovered that (I only think this one image because I can't try the old ones 😅) refuse to accept config in every form, trough env var some is ignored some cause error.At the same time the config file once bind causes a null point exception to be thrown
@mageddo commented on GitHub (Oct 25, 2024):
@SiriosDev can you elaborate an example for this issue you are getting? I made some tests and couldn´t reproduce
@SiriosDev commented on GitHub (Oct 27, 2024):
Yep, this is my example, putting any kind of env var, the resulting container is always the same, with the pre set entry (
dps-sample.dev), no domain etc etc@SiriosDev commented on GitHub (Oct 27, 2024):
while with this (removing the env in the compose)
and this config.json
these errors appear:
@mageddo commented on GitHub (Oct 28, 2024):
Got this, that's a different issue, the cause of the issue is the following line
You need to specify a protocol, like:
Do you really need to specify that docker host? you can just not pass it and let DPS use
/var/run/docker.sock@SiriosDev commented on GitHub (Oct 28, 2024):
Yes cause otherwise point to the wrong ip
Specifying the protocol start correctly, but not resolve nothing (of the docker hostnames, ex: trying to ping/dig dps itself) anymore, and trying to resolve the host address (in my case
host.dkr) throw a null exception here a log:@mageddo commented on GitHub (Oct 28, 2024):
I'm afraid the container is not able to ping
192.168.1.253?@SiriosDev commented on GitHub (Oct 28, 2024):
Theoretically yes, but practically I can't test it with ping because via
docker execI can't execute anything except./dns-proxy-server <args>all the other containers can so I am 90% sure
@mageddo commented on GitHub (Oct 28, 2024):
You can do something as follows
@SiriosDev commented on GitHub (Oct 28, 2024):
ok, tested, perfectly reachable very strange
@SiriosDev commented on GitHub (Nov 9, 2024):
so?
@mageddo commented on GitHub (Nov 19, 2024):
I don't know how to help at this point