conf-path opens a nonexistent file

[9yx]

What is Happening

Start dps with -conf-path=/etc/dns-proxy-server/config.json, (dps location /usr/bin/dns-proxy-server)

when start dps open config /usr/bin/etc/dns-proxy-server/config.json

What is expected

Open config /etc/dns-proxy-server/config.json

Steps to Reproduce

Start:

/usr/bin/dns-proxy-server -conf-path=/etc/dns-proxy-server/config.json

Specs:

• OS: Archlinux
• Docker Version: 19.03.5-ce
• DPS Version: 2.18.7

$ /usr/bin/dns-proxy-server -conf-path=/etc/dns-proxy-server/config.json
2020/01/13 13:02:16.003274 ERROR f=local.go:123 pkg=github.com/mageddo/dns-proxy-server/events/local m=storeDefaultConfig status=error-to-create-conf-path, path=/usr/bin/etc/dns-proxy-server/config.json
2020/01/13 13:02:16.003354 ERROR f=local.go:123 pkg=github.com/mageddo/dns-proxy-server/events/local m=storeDefaultConfig status=error-to-create-conf-path, path=/usr/bin/etc/dns-proxy-server/config.json

[mageddo]

Looks like -conf-path feature wasn't designed to support absolute paths, I think it makes sense to support it.

dns-proxy-server/utils/utils.go

Lines 168 to 177 in 632d36a

	func GetPath(path string) string {
	if !strings.HasPrefix(path, "/") {
	path = "/" + path
	}
	currentPath := GetCurrentPath();
	if strings.HasSuffix(currentPath, "/") {
	currentPath = currentPath[0:len(currentPath)-1]
	}
	return currentPath + path
	}