cmj2002/warp-docker

Run Cloudflare WARP in Docker.

cmj2002

正在南京大学学习人工智能

博客：blog.caomingjun.com

邮箱：[email protected]

warp-docker's Issues

能否配合其他大佬的脚本进行每段时间后自动优选ip呢

感谢开源这么好用的docker
warp-cli 有这个设置自定义endpoint功能

warp-cli tunnel endpoint set <ENDPOINT>

能否配合其他大佬的脚本进行每段时间后自动优选ip呢？例如
https://gitlab.com/Misaka-blog/warp-script/-/raw/main/files/warp-yxip/warp-yxip.sh

优选ip对网速的提升有很大的效果

能否使用chatgpt-web重定向到wrap-docker来访问chatgpt?

比如在: chatgpt-web的docker配置的proxy之类的地方设置该地址, 然后通过这个warp的网络来访问chatgpt?

arm64版本

您好，是否有可能提供arm64版本的镜像，谢谢！

Cannot connect to gost because Warp is grabbing incoming traffic

Inside container

warp@1db191c9c609:/$ curl --socks5-hostname 127.0.0.1:1080 https://cloudflare.com/cdn-cgi/trace
fl=636f241
h=cloudflare.com
ip=8.29.109.153
ts=1720827095.986
visit_scheme=https
uag=curl/7.81.0
colo=FRA
sliver=none
http=http/2
loc=DE
tls=TLSv1.3
sni=plaintext
warp=on
gateway=on
rbi=off
kex=X25519

Outside container

❯ curl --socks5-hostname 127.0.0.1:1080 https://cloudflare.com/cdn-cgi/trace -v
*   Trying 127.0.0.1:1080...
* Connected to 127.0.0.1 (127.0.0.1) port 1080
* Recv failure: Connection reset by peer
* SOCKS: Failed receiving initial SOCKS5 response: Failure when receiving data from the peer
* Closing connection
curl: (97) Recv failure: Connection reset by pee

Once I kill warp-svc process inside container, then previous command works (but then it doesn't go through cloudfare network of course).

Do you have any advice what to do in this case?

Can't complete SOCKS5 connection

Hi, I am reaching out to report an issue I encountered while running a Docker Compose file. Specifically, when I run the following Docker Compose configuration

version: "3.9"

services:
  warp:
    image: caomingjun/warp
    container_name: warp
    restart: always
    ports:
      - '1080:1080'
    environment:
      - WARP_SLEEP=2
      - WARP_LICENSE_KEY=<OBSECURED>
    cap_add:
      - NET_ADMIN
    sysctls:
      - net.ipv6.conf.all.disable_ipv6=0
      - net.ipv4.conf.all.src_valid_mark=1
    volumes:
      - ${DATA_PATH}/cloudflare-warp:/var/lib/cloudflare-warp

The container runs successfully and appears to be healthy. However, when I attempt to execute the command curl --socks5 127.0.0.1:1080 https://cloudflare.com/cdn-cgi/trace within the warp container and the host, it returns the following error: curl: (97) Can't complete SOCKS5 connection to www.cloudflare.com. (4)

I have verified that the necessary environment variables. Could you please assist me in understanding why the SOCKS5 connection is not functioning as expected within the warp container? I have reviewed the documentation and searched for similar issues, but haven't found a solution yet.

Additionally, I would like to mention that my network connection is working properly, as I am able to access other websites and services without any issues.

Thank you for your attention to this matter.

重启了一下机器 容器起不来了

dbus-daemon[12]: Failed to start message bus: The pid file "/run/dbus/pid" exists, if the message bus is not running, remove this file

容器没起来 进不去终端 不知如何删除

在docker-compose中，别的应用该怎样设置socks代理呢

version: '3'

services:
  ninja:
    image: zhuxindong/ninja:latest
    container_name: ninja
    restart: unless-stopped
    environment:
      - TZ=Asia/Shanghai
      - PROXIES=socks5://127.0.0.1:10801
      # - CONFIG=/serve.toml
      # - PORT=8080
      # - HOST=0.0.0.0
      # - TLS_CERT=
      # - TLS_KEY=
    # volumes:
      # - ${PWD}/ssl:/etc
      # - ${PWD}/serve.toml:/serve.toml
    command: serve run
    ports:
      - "8080:7999"
    depends_on:
      - warp

  warp:
    image: caomingjun/warp
    container_name: warp
    restart: always
    ports:
      - '10801:1080'
    environment:
      - WARP_SLEEP=2
      - WARP_LICENSE_KEY=
    cap_add:
      - NET_ADMIN
    sysctls:
      - net.ipv6.conf.all.disable_ipv6=0
      - net.ipv4.conf.all.src_valid_mark=1
    volumes:
      - ./data:/var/lib/cloudflare-warp

我的另一个容器设置- PROXIES=socks5://127.0.0.1:10801 是否正确？还是说设置成 - PROXIES=socks5://warp:10801

warp-cli status always manual disconnection

Hi,
I tried to use this docker, but it doesnt seems working. I have successfully register the device, however when I check with warp-cli status, it always showing the warp is off.

tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519

Can anyone help me?

Failed to load Registration error=OsError(Os { code: 2, kind: NotFound, message: "No such file or directory" })

一开始以为是ipv6问题, 但删除文件夹重建还是会这样, 它依旧并没有创建setting.json, config.json之类的, 反而反反复复重启.

How to set warp plus

i have these:

Does these can be applied in docker-compose file ? which one is related to WARP_LICENSE_KEY ?

可以支持Cloudflare Zero Trust吗？

新版2024.4.133-2.11.5的team无法使用需要增加--accept-tos

把
sudo warp-svc &
这行改为
sudo warp-svc --accept-tos &
即可

直接使用会有什么次数或流量限制吗?

如果有, 那在什么地方(如Environment)输入用户名或密码来让注册用户使用更多流量的选项, 会不会更好一些?
感谢.

最近忽然失效了

之前一直用着没问题，最近几天忽然发现用不了了。不需要翻墙网址还能打开，需要翻墙的不行了。

Access warp-docker from remote

I'm trying to access warp-docker on a host machine from a remote machine.

My firewall seems to allow 1080 but port scanning times out and I can't use the test curl from the remote machine using host ip.

Is there any special setup with the container that I need to do to connect remotely?

Goal: remote connect to host (running warp-docker) to route traffic through the container.

For what it's worth everything works in docker/containers are able to access and use.

Request for ARM64 Image Support in Docker Container

Hello,

I am writing to kindly request your support in adding an ARM64 image for the caomingjun/warp container. Currently, the container does not have support for this platform. If you have the time, I kindly request your consideration in incorporating it.

Thanks!

当我在容器启动时候指定了外部network，流量代理就失效了。

在docker-compose.yml中，我添加了

networks:
default:
name: mynetwork
external: true

mynetwork 是bridge
容器启动正常，warp状态也正常，只是做代理流量的时候失效了。抓了包，似乎握手都没有建立成功。

Dockerfile实现方式讨论

非常感谢作者的优秀项目。

但是在使用你的docker时，由于你的 warp-svc 不是主进程，导致warp-svc挂了也必须要等 HEALTHCHECK 重试 3次失败，间隔15秒，至少1分钟之后，容器才会重启。

我在你的基础上改良了一下，将 warp-svc 作为主进程，另写了一个 subscript.sh 作为子进程，通过死循环的形式，检查 warp-svc 是否已启动成功，成功就进行检查注册、注册licence、connect 后退出。

healthcheck仅作为检查warp的健康状态，以及gost保活。

由于我是自用，代码写得比较糙，就不提PR了。写此 issues，仅为技术讨论，如果对你有用，可以按我的思路改良，如果没用，请忽视我就好。

我的项目地址： https://github.com/edwinhuish/warp-docker

无法远程连接socks5

你好,搭建成功后运行curl --socks5 127.0.0.1:1080 https://cloudflare.com/cdn-cgi/trace 回显warp=on正常
在其他主机使用这个socks5.提示无法连接curl: (28) Failed to connect to test.host.com port 9696 after 15461 ms: Couldn't connect to server
运行docker ps查看监听的是0.0.0.0
ce962203bbf2 caomingjun/warp "/entrypoint.sh" 3 minutes ago Up 3 minutes (healthy) 0.0.0.0:9696->1080/tcp, :::9696->1080/tcp warp

nftables and firewall issues on Synology NAS

Hello,

With latest image I get this error on a Synology NAS:

2024-03-04T10:36:29.807Z DEBUG firewall: Firewall allow managed network endpoints managed_network_endpoints=[]
2024-03-04T10:36:29.807Z INFO firewall: Firewall starting
2024-03-04T10:36:29.813Z WARN firewall::linux: Failed to set firewall rules via stdin. Retrying using temporary file exit_code=ExitStatus(unix_wait_status(256))
2024-03-04T10:36:29.824Z ERROR firewall::linux: Failed to start firewall with exit code: exit status: 1
2024-03-04T10:36:29.824Z WARN firewall: fw.apply_rules failed e=ApplyError("nft command failed with return code: 256")
2024-03-04T10:36:29.825Z WARN main_loop: warp::warp_service: Unable to update firewall on disconnect e=ApplyError("nft command failed with return code: 256")
2024-03-04T10:36:29.825Z DEBUG main_loop: warp::warp_service: Determining disconnected reason from connectivity state net_info=IPv4: [eth0; 172.18.0.15; Ethernet]; DNS servers:; 127.0.0.11:53;
power_state=None disconnect_reason=None
2024-03-04T10:36:29.825Z WARN main_loop: warp::warp_service: Disconnecting, but reason is unknown
2024-03-04T10:36:29.825Z WARN main_loop: warp::warp_service: Reconnect on settings change failed error=FirewallUpdateFailed(ApplyError("nft command failed with return code: 256"))

With previous caomingjun/warp:2023-07-18 everything is ok.

I search for error "nft command failed with return code: 256" but I can't figure out how to fix it.

Seems that with latest version now it's necessary to add this volume:
/run/dbus/system_bus_socket:/run/dbus/system_bus_socket

I tried to build my own Dockerfile based on latest Ubuntu or Debian, delete Gost proxy, but nft error is still here.

Can you help me ? Thanks.

你好，官方客户端有内存泄露的问题，这个docker镜像存在这个问题吗？