I am using the version 3.2.6.
When we specify the full path of the unix domain socket on the command line, the configuration generated internally is not valid and we cannot access the service.
Here is a reproduction case:
# This is NOT valid
$ ./gost -L tcp://:8080 -F unix:///var/run/docker.sock -O yaml
services:
- name: service-0
addr: :8080
handler:
type: tcp
chain: chain-0
listener:
type: tcp
chains:
- name: chain-0
hops:
- name: hop-0
# But this is ok:
$ ./gost -L tcp://:8080 -F unix://docker.sock -O yaml
services:
- name: service-0
addr: :8080
handler:
type: tcp
chain: chain-0
listener:
type: tcp
chains:
- name: chain-0
hops:
- name: hop-0
nodes:
- name: node-0
addr: docker.sock
connector:
type: unix
dialer:
type: unix
tls:
serverName: docker.sock
I am using the version 3.2.6.
When we specify the full path of the unix domain socket on the command line, the configuration generated internally is not valid and we cannot access the service.
Here is a reproduction case: