Vasilii Blazhnov
Vasilii Blazhnov
As I have gotten from `entrypoint.sh` https://github.com/umputun/nginx-le/blob/f9dd2c435a02dae020237a5b83c2924e086115b8/script/entrypoint.sh#L22 changing conf file outside the container does not affect the real nginx's conf file, isn't it? Or I misunderstood you and you are...
Yes, of course. The problem is connections drop. May be it will be useful for someone here: in a case when I need small changes I just go inside container...
As for me, it's mainly interesting for MongoDB + API. Do you want to keep the same LogEntry structure for syslog and other storages?
I manage to reproduce it consistently, it repdocues on both v5 and v6 servers. ### Env ``` # go version go version go1.18.1 linux/amd64 # go env GO111MODULE="on" GOARCH="amd64" GOBIN=""...
Found another way to bypass the problem: disabling CGO. `CGO_ENABLED=0 GOFLAGS=-buildvcs=false make` builds working plugin without removing `-trimpath`
@mkraft I didn't mean whole object to pass, but only `props` field. According to the code I linked above you can not pass such a valid JSON object there ```...
@mkraft it's better to add "help wanted" tag
I would expect no "Illegal instruction" output