Yet another unofficial v2ray server container with x86 and arm/arm64 (Raspberry Pi) support.
$ git clone https://github.com/samuelhbne/server-v2ray.git
$ cd server-v2ray
$ docker build -t samuelhbne/server-v2ray:amd64 -f Dockerfile.amd64 .
...- Please replace "amd64" with the arch match the current box accordingly. For example: "arm64" for AWS ARM64 platform like A1, t4g instance or 64bit Ubuntu on Raspberry Pi. "arm" for 32bit Raspbian.
$ docker run --rm -it samuelhbne/server-v2ray:amd64
server-v2ray -u|--uuid <vmess-uuid> [-p|--port <port-num>] [-l|--level <level>] [-a|--alterid <alterid>] [-k|--hook hook-url] [--wp <websocket-path>] [--nginx <domain-name>] [--nginx-port <port-num>] [--share-cert <cert-path>] [--no-ssl]
-u|--uuid <vmess-uuid> Vmess UUID for initial V2ray connection
-p|--port <port-num> [Optional] V2ray listening port, default 10086
-l|--level <level> [Optional] Level number for V2ray service access, default 0
-a|--alterid <alterid> [Optional] AlterID number for V2ray service access, default 16
-k|--hook <hook-url> [Optional] URL to be hit before server execution, for DDNS update or notification
--wp <websocket-path> [Optional] Enable websocket with given websocket-path, e.g. '/wsocket'
--nginx <domain-name> [Optional] Enable Ngnix frontend with given domain-name, must be applied with --wp enabled
--nginx-port <port-num> [Optional] Ngnix listening port, default 443, must be applied with --nginx enabled
--cert <cert-path> [Optional] Reading TLS cert and key from given path instead of requesting
--no-ssl [Optional] Disable Ngnix SSL support for CDN optimisation, must be applied with --nginx enabled
$ docker run --name server-v2ray -p 8443:443 -v /home/ubuntu/mydomain.duckdns.org:/opt/mydomain.duckdns.org -d samuelhbne/server-v2ray:amd64 -u bec24d96-410f-4723-8b3b-46987a1d9ed8 -p 10086 -k https://duckdns.org/update/mydomain/c9711c65-db21-4f8c-a790-2c32c93bde8c --wp /wsocket --nginx mydomain.duckdns.org --nginx-port 443 --cert /opt/mydomain.duckdns.org
...- Please replace "amd64" with the arch match the current box accordingly. For example: "arm64" for AWS ARM64 platform like A1, t4g instance or 64bit Ubuntu on Raspberry Pi. "arm" for 32bit Raspbian.
- Please replace "8443" with the TCP port number you want to listen.
- Please replace "bec24d96-410f-4723-8b3b-46987a1d9ed8" with the uuid you want to set for V2ray client auth.
- Please replace /home/ubuntu/mydomain.duckdns.org with the folder where TLS cert saved.
- If not appointed by '--cert' option, server-v2ray will request a new TLS cert from Letsencrypt
- You can optionally assign a HOOK-URL to update the DDNS domain-name pointing to the current server public IP address.
Try to connect the server from v2ray compatible mobile app like v2rayNG for Android or Shadowrocket for iOS with the host-name, port, UUID, alterid etc. set above. Or verify it from Ubuntu / Debian / Raspbian client host follow the instructions below.
$ docker run --rm -it samuelhbne/proxy-v2ray:amd64
proxy-v2ray -h|--host <v2ray-host> -u|--uuid <vmess-uuid> [-p|--port <port-num>] [-l|--level <level>] [-a|--alterid <alterid>] [-s|--security <client-security>] [--wp <websocket-path>] [--sni <sni-hostname>] [--no-ssl]
-h|--host <v2ray-host> V2ray server host name or IP address
-u|--uuid <vmess-uuid> Vmess UUID for initial V2ray connection
-p|--port <port-num> [Optional] Port number for V2ray connection, default 443
-l|--level <level> [Optional] Level number for V2ray service access, default 0
-a|--alterid <alterid> [Optional] AlterID number for V2ray service access, default 16
-s|--security <client-security> [Optional] V2ray client security setting, default 'auto'
--wp <websocket-path> [Optional] Connect via websocket with given websocket-path, e.g. '/wsocket'
--sni <sni-hostname> [Optional] SNI hostname when connect via websocket, default same as v2ray-host
--no-ssl [Optional] Disable ssl support when connect via websocket, only for testing
$ docker run --name proxy-v2ray -p 1080:1080 -p 65353:53/udp -p 8123:8123 -d samuelhbne/proxy-v2ray:amd64 -h 12.34.56.78 -p 8443 -u bec24d96-410f-4723-8b3b-46987a1d9ed8 --wp /wsocket --sni mydomain.duckdns.org
...
$ curl -sSx socks5h://127.0.0.1:1080 http://ifconfig.co
12.34.56.78- First we ran proxy-v2ray as SOCKS5 proxy that tunneling traffic through your v2ray server.
- Then launching curl with client-IP address query through the proxy.
- This query was sent through your server with server-v2ray running.
- You should get the public IP address of your server with server-v2ray running if all good.
- Please have a look over the sibling project proxy-v2ray for more details.
$ docker stop server-v2ray
...
$ docker rm server-v2ray
...