David Wang

append "-v 10" at the end of your command, it should tell where is wrong. The tool would exit with success code when it has done nothing.......

I tried on alpine-docker 3.7, with /etc/resolv.conf as follow: ``` nameserver 10.254.0.100 search localdomain somebaddomain options ndots:5 ``` My DNS server "10.254.0.100" manage its own domain 'localdomain' while forward query...

I tried following changes, it seems work. (Tried on my cluster and push to davidzqwang/alpine-dns:3.7) ``` diff --git a/src/network/lookup_name.c b/src/network/lookup_name.c index 209c20f..abb7da5 100644 --- a/src/network/lookup_name.c +++ b/src/network/lookup_name.c @@ -202,7 +202,7...

I am not sure, but if somehow a failure reported, would the test report log the line indicating which test step failed or just refer to the line within the...

> `t.Helper()` does the trick: > > ``` > root@fbf8cd893314:/go/src/github.com/docker/docker# go test -run TestNetworkDBNodeJoinLeaveIteration ./libnetwork/networkdb/ > --- FAIL: TestNetworkDBNodeJoinLeaveIteration (3.81s) > networkdb_test.go:510: timeout hit after 3s: current number of nodes...

I am using 2.7.0, sometimes when log file removed and then recreated, promtail would stuck and no log read afterward. Promtail log shows following sequence: ``` ts=2022-12-20T06:39:51.126377231Z caller=log.go:168 level=info msg="Waiting...

After fix the silly retry countdown bug, following logs show up ``` Dec 21 06:00:22 iZuf6h6buntpmoj3kqqdrgZ promtail[17833]: level=info ts=2022-12-20T22:00:22.259371564Z caller=tailer.go:159 component=tailer msg="tail routine: tail channel closed, stopping tailer" path=****.log reason="gave...