-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running another service in warp docker #28
Comments
Docker engine fully manages If you can access the shell in container, you can try to see if
To be honest, I can't understand the content. I haven't changed it; the Docker engine is managing it. In addition, WARP will output many |
Here is the full log when I run the container
here is the output of resolv.conf |
The What's the output of |
I have also tried to run the docker image |
I am sorry, when I said that this warning did not appear in my logs, I was not running the latest version of the image. I just ran the latest version, and the I found nft errors in your log, this might be a nft problem.
We already have a unsolved nft issue for Synology NAS (#16). If your RSS bot can use socks, I suggest removing GOST and use WARP's own local proxy mode instead, which stops WARP from messing with nft. (In fact, I installed GOST in the container to allow the users to use custom proxy protocol. If you don't need it, WARP's local proxy might be a better choice) |
Modified warp to use local proxy but cannot get past this. also tried adding --accept-tos |
I am not very clear about which commands require accepting the TOS. My Dockerfile uses |
Hi I was trying to run my RSS bot inside the warp docker and I want the bot to use the warp traffic. Since I don't have a VPS I cannot use docker-compose. The platform I tried only has docker. So when I run my bot with the warp docker I get this error.
Thanks
WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
The text was updated successfully, but these errors were encountered: