cmj2002
commented
2 weeks ago Docker engine fully manages /etc/resolv.conf inside the container, and most of the other details of the networking environment. This is more likely a platform-specific issue, as the platform you are using is running Docker containers in a way that differs from the Docker engine and has affected resolv.conf.
If you can access the shell in container, you can try to see if /etc/resolv.conf exists and check its owner and content. Here is mine as a reference.
warp@2544698bb855:/$ ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 144 Aug 22 09:40 /etc/resolv.conf
warp@2544698bb855:/$ cat /etc/resolv.conf
# This file was generated by cloudflare-warp.
nameserver 127.0.2.2
nameserver 127.0.2.3
search .
options ndots:0
options edns0
options trust-adTo 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 WARN messages, and a single warning does not necessarily cause an issue (although I searched my logs and did not find your warning). The problem may not even occur in WARP; if you can access the container's shell, be sure to use curl to check whether you are accessing the internet through WARP.
pohfow
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