socat listen port about warp-svc HOT 6 OPEN

Hi
What is your use case?
You can change the public port in docker run or docker compose.
For example use this:
9999:1080

from warp-svc.

I'm using XRay (Marzban, 3x-ui), port 1080 is used for the shadowsocks protocol (standard port)

{
"tag": "Shadowsocks TCP",
"listen": "0.0.0.0",
"port": 1080,
"protocol": "shadowsocks",
"settings": {
"clients": [],
"network": "tcp,udp"
}

fro entrypoint.sh:

socat tcp-listen:1080,reuseaddr,fork tcp:localhost:40000 &

netstat -plnut

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:1080 0.0.0.0:* LISTEN 316054/socat

from warp-svc.

create a directory:

mkdir warp
cd warp

create a docker-compose.yml file with this content:

version: "3"
services:
  warp:
    image: aleskxyz/warp-svc:latest
    environment:
      WARP_LICENSE: xxxxxxxx-xxxxxxxx-xxxxxxxx
    ports:
    - 127.0.0.1:2323:1080
    restart: always
    volumes:
    - ./warp:/var/lib/cloudflare-warp

run docker compose:

docker compose up -d

Now you can use socks on 127.0.0.1:2323 and use it in xray

from warp-svc.

does not work
port 1080 is busy a socat from docker

from warp-svc.

https://github.com/SuperNG6/docker-warp-proxy/blob/5298005de6e82825ffd9ef32633c34180e2d55f8/entrypoint.sh#L14C20-L14C20

https://github.com/SuperNG6/docker-warp-proxy

from warp-svc.

Hello, I support adding an environment variable to control the listening port of socat.

When I use --net=host so that WARP can use the host's IPv6 network stack, I cannot change the listening port using docker's port mapping, and 1080 is a very common port that is prone to conflicts.

from warp-svc.