Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Running another service in warp docker #28

Open
pohfow opened this issue Aug 26, 2024 · 7 comments
Open

Running another service in warp docker #28

pohfow opened this issue Aug 26, 2024 · 7 comments

Comments

@pohfow
Copy link

pohfow commented Aug 26, 2024

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
@cmj2002
Copy link
Owner

cmj2002 commented Aug 26, 2024

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-ad

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 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
Copy link
Author

pohfow commented Aug 26, 2024 •
edited
Loading 

2024-08-26T07:33:32.761Z  INFO warp::warp_service: Version: 2024.6.497
2024-08-26T07:33:32.762Z ERROR warp::warp_service::ipc_cleanup: Could not read the WARP diag partials directory err=Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-08-26T07:33:32.774Z DEBUG warp_settings::raw_settings: Loading settings from file "/var/lib/cloudflare-warp/settings.json"
2024-08-26T07:33:32.774Z  INFO warp_settings::manager: User preferences not loaded e=No such file or directory (os error 2)
2024-08-26T07:33:32.775Z DEBUG warp_settings::manager: Starting local policy file watch parent_path="/var/lib/cloudflare-warp"
2024-08-26T07:33:32.775Z  WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
2024-08-26T07:33:32.776Z DEBUG dex::status: Starting API request loop
2024-08-26T07:33:32.776Z DEBUG warp::warp_service: Main loop refactor feature disabled
2024-08-26T07:33:32.777Z DEBUG watchdog: warp::watchdog: Kicking off watchdog
2024-08-26T07:33:32.777Z  INFO main_loop: warp_net::ipc: Bound ipc socket name="cloudflare-warp/warp_service" path="/run/cloudflare-warp/warp_service"
2024-08-26T07:33:32.777Z  INFO main_loop: warp::warp_service: Warp IPC listening on "cloudflare-warp/warp_service"
2024-08-26T07:33:32.777Z  INFO firewall: Firewall engine running
2024-08-26T07:33:32.777Z  WARN main_loop: warp::warp_service: Failed to load Registration error=OsError(Os { code: 2, kind: NotFound, message: "No such file or directory" })
2024-08-26T07:33:32.781Z DEBUG warp_api::addresses: Caching initial API IPs consumer=[104.16.80.230, 104.17.143.163, 2606:4700::6811:8fa3, 2606:4700::6810:50e6] teams=[162.159.137.105, 162.159.138.105, 2606:4700:7::a29f:8969, 2606:4700:7::a29f:8a69]
2024-08-26T07:33:32.781Z DEBUG warp::warp_api: Sending API request GET api.cloudflareclient.com./v0/client_config
2024-08-26T07:33:32.782Z DEBUG warp::warp_api: Sending API request GET zero-trust-client.cloudflareclient.com./v0/client_config
2024-08-26T07:33:32.810Z DEBUG run: warp_settings::manager: LayerManager update: NetworkDefaults(NetworkDefaults { split_config: Some(Exclude { ips: [(10.0.0.0/8, None), (100.64.0.0/10, None), (169.254.0.0/16, None), (172.16.0.0/12, None), (192.0.0.0/24, None), (192.168.0.0/16, None), (224.0.0.0/24, None), (240.0.0.0/4, None), (239.255.255.250/32, None), (255.255.255.255/32, None), (fe80::/10, None), (fd00::/8, None), (ff01::/16, None), (ff02::/16, None), (ff03::/16, None), (ff04::/16, None), (ff05::/16, None), (fc00::/7, None)], hosts: [] }) })
2024-08-26T07:33:32.810Z DEBUG main_loop: warp::warp_service: Checking for registration vs settings account mismatch reg_is_teams=false settings_is_teams=false reg_org=None settings_org=None
2024-08-26T07:33:32.810Z  INFO firewall: Firewall stopped
2024-08-26T07:33:32.810Z  INFO main_loop: warp::warp_service: New User Settings
2024-08-26T07:33:32.810Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC update: SettingsUpdated
2024-08-26T07:33:32.810Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseUpdate: SettingsUpdated
2024-08-26T07:33:32.810Z DEBUG main_loop: warp::warp_service: update_settings: no restart required
2024-08-26T07:33:32.811Z  WARN main_loop: network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
2024-08-26T07:33:32.811Z  INFO warp::warp_service: Spawning registration changed IPC loop
2024-08-26T07:33:32.813Z DEBUG network_info::linux::power_notifier: Initializing dbus connection
2024-08-26T07:33:32.813Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="status_change"
2024-08-26T07:33:32.814Z  INFO main_loop: warp::warp_service: WARP status: Unable(RegistrationMissing)
2024-08-26T07:33:32.814Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC status update: Unable(RegistrationMissing)
2024-08-26T07:33:32.814Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseStatus: Unable(RegistrationMissing)
2024-08-26T07:33:32.814Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="settings_changed"
2024-08-26T07:33:32.814Z DEBUG main_loop: warp::warp_service: Checking for registration vs settings account mismatch reg_is_teams=false settings_is_teams=false reg_org=None settings_org=None
2024-08-26T07:33:32.814Z  INFO firewall: Firewall stopped
2024-08-26T07:33:32.814Z  INFO main_loop: warp::warp_service: User Settings Changed: {}
2024-08-26T07:33:32.814Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC update: SettingsUpdated
2024-08-26T07:33:32.814Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseUpdate: SettingsUpdated
2024-08-26T07:33:32.814Z DEBUG main_loop: warp::warp_service: update_settings: no restart required
2024-08-26T07:33:34.717Z  WARN warp_net::ipc::unix: Failed to get path for client error="return code = -1, errno = 13, message = 'Permission denied'" pid=50
2024-08-26T07:33:34.718Z  WARN warp_net::ipc::unix: Failed to get path for client error="return code = -1, errno = 13, message = 'Permission denied'" pid=50
2024-08-26T07:33:34.718Z  INFO warp::warp_service::ipc_loop: IPC: new connection exec_context=Regular process_name="<Unknown>" pid=50
2024-08-26T07:33:34.719Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 6d6dec7b-f883-4d62-adf7-baebec8765d4; GetAppSettings
2024-08-26T07:33:34.722Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 10f4b6f2-b9db-484f-ba7b-a73061a76469; GetAccount
2024-08-26T07:33:34.722Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: 10f4b6f2-b9db-484f-ba7b-a73061a76469; Error: Missing registration. Try running: "warp-cli registration new"
2024-08-26T07:33:34.723Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: c090d57a-48d7-4c70-a099-855e8ef0ae61; NewRegistration
2024-08-26T07:33:34.723Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC update: RegistrationInProgress
2024-08-26T07:33:34.723Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseUpdate: RegistrationInProgress
2024-08-26T07:33:34.723Z DEBUG warp::warp_service::ipc_handlers: Sending IPC update: ConfigurationUpdated
2024-08-26T07:33:34.723Z DEBUG warp::warp_service::ipc_handlers: Ipc Broadcast ResponseUpdate: ConfigurationUpdated
2024-08-26T07:33:34.723Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="registration_change"
2024-08-26T07:33:34.725Z ERROR device_posture::linux: Failed to load SMBiosData error=Os { code: 2, kind: NotFound, message: "No such file or directory" }
2024-08-26T07:33:34.725Z DEBUG warp::warp_api: Sending API request POST api.cloudflareclient.com./v0/reg
2024-08-26T07:33:35.478Z DEBUG warp::warp_api::registration: Warp endpoint override ports ports=[2408, 500, 1701, 4500]
2024-08-26T07:33:35.478Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="api_responses"
2024-08-26T07:33:35.478Z DEBUG run: warp_settings::manager: LayerManager update: NetworkPolicy(None)
2024-08-26T07:33:35.478Z DEBUG main_loop: warp::warp_service::api_handlers: Registration updated current_registration=NewInProgress disposition=UpdateOnly
2024-08-26T07:33:35.479Z DEBUG main_loop: warp::warp_service::api_handlers: Registration updated 0.00 hours old, refresh at 2024-08-27 7:33:35.478116951 +00:00:00
Registration: 71d128f2-1dda-45ff-8dfe-2b8d74b0aa84
Auth Method: Consumer
Public key: 6336387a64385356333355344252355059434f6d6d42625074543653697173564d446f58497155306c6e383d
Interface: WarpEndpoint { v4: 172.16.0.2, v6: 2606:4700:110:8241:a231:8b06:7bf0:16e8 }
Endpoints: [WarpSocketAddrPair { v4: 162.159.192.2:2408, v6: [2606:4700:d0::a29f:c002]:2408 }, WarpSocketAddrPair { v4: 162.159.192.2:500, v6: [2606:4700:d0::a29f:c002]:500 }, WarpSocketAddrPair { v4: 162.159.192.2:1701, v6: [2606:4700:d0::a29f:c002]:1701 }, WarpSocketAddrPair { v4: 162.159.192.2:4500, v6: [2606:4700:d0::a29f:c002]:4500 }]
Subnet CIDRS: None

Account: Free { id: AccountId(62357dfe-72b3-4bb2-bf71-02548aaef8ae), license: "X1I62yi8-4URG20u9-ju69P4V1" }

2024-08-26T07:33:35.479Z  INFO main_loop: warp::warp_api::storage: Saving registration cache with config_name=None
2024-08-26T07:33:35.480Z DEBUG warp::warp_service::ipc_handlers: Sending IPC update: ConfigurationUpdated
2024-08-26T07:33:35.480Z DEBUG warp::warp_service::ipc_handlers: Ipc Broadcast ResponseUpdate: ConfigurationUpdated
2024-08-26T07:33:35.480Z  INFO firewall: Firewall stopped
2024-08-26T07:33:35.480Z DEBUG main_loop: warp::warp_service: Determining disconnected reason from connectivity state net_info=IPv4: [eth0; 172.17.0.2; Ethernet]; DNS servers:;   8.8.8.8:53;   8.8.4.4:53;
 power_state=None disconnect_reason=None
2024-08-26T07:33:35.481Z  WARN main_loop: warp::warp_service: Disconnecting, but reason is unknown
2024-08-26T07:33:35.481Z DEBUG main_loop: warp::warp_service: Checking for registration vs settings account mismatch reg_is_teams=false settings_is_teams=false reg_org=None settings_org=None
2024-08-26T07:33:35.481Z  INFO firewall: Firewall stopped
2024-08-26T07:33:35.481Z  INFO main_loop: warp::warp_service: User Settings Changed: {}
2024-08-26T07:33:35.481Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC update: SettingsUpdated
2024-08-26T07:33:35.481Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseUpdate: SettingsUpdated
2024-08-26T07:33:35.481Z DEBUG main_loop: warp::warp_service: update_settings: no restart required
2024-08-26T07:33:35.482Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: c090d57a-48d7-4c70-a099-855e8ef0ae61; Success
Success
2024-08-26T07:33:35.482Z  INFO warp::warp_service::ipc_loop: IPC connection ended
Warp client registered!
2024-08-26T07:33:35.483Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="status_change"
2024-08-26T07:33:35.484Z  INFO main_loop: warp::warp_service: WARP status: Disconnected(Manual)
2024-08-26T07:33:35.484Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC status update: Disconnected(Manual)
2024-08-26T07:33:35.484Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseStatus: Disconnected(Manual)
2024-08-26T07:33:35.484Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="registration_change"
2024-08-26T07:33:35.484Z DEBUG main_loop: warp::warp_service: Determining disconnected reason from connectivity state net_info=IPv4: [eth0; 172.17.0.2; Ethernet]; DNS servers:;   8.8.8.8:53;   8.8.4.4:53;
 power_state=None disconnect_reason=None
2024-08-26T07:33:35.484Z  WARN main_loop: warp::warp_service: Disconnecting, but reason is unknown
2024-08-26T07:33:35.506Z  WARN warp_net::ipc::unix: Failed to get path for client error="return code = -1, errno = 13, message = 'Permission denied'" pid=51
2024-08-26T07:33:35.506Z  WARN warp_net::ipc::unix: Failed to get path for client error="return code = -1, errno = 13, message = 'Permission denied'" pid=51
2024-08-26T07:33:35.506Z  INFO warp::warp_service::ipc_loop: IPC: new connection exec_context=Regular process_name="<Unknown>" pid=51
2024-08-26T07:33:35.507Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 600812e3-8280-434b-bbc9-1a50cacfb9db; GetAppSettings
2024-08-26T07:33:35.507Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 322006d7-c95f-47ab-9372-49e42e621cac; GetAccount
2024-08-26T07:33:35.507Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: 322006d7-c95f-47ab-9372-49e42e621cac; Registration: ID: 71d128f2-1dda-45ff-8dfe-2b8d74b0aa84; Public Key: 73af3377c495df7538051e4f6023a69816cfb53e928aab15303a1722a534967f; Managed: false; Account: Free { id: AccountId(62357dfe-72b3-4bb2-bf71-02548aaef8ae), license: "X1I62yi8-4URG20u9-ju69P4V1" };Alternate networks: None
2024-08-26T07:33:35.508Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 31cb7cce-6b91-4522-ad1d-2db9e67ed0d5; SetAlwaysOn(true)
2024-08-26T07:33:35.508Z  INFO main_loop: structlog: event="UserToggledV0" toggle="on" warp_colo="none" warp_metal="none"
2024-08-26T07:33:35.511Z DEBUG run: warp_settings::manager: LayerManager update: UserOverrides(<mutator>)
2024-08-26T07:33:35.511Z DEBUG run: warp_settings::manager: UserOverrides updated: UserOverrides { version: None, always_on: Some(true), operation_mode: None, disable_for_wifi: None, disable_for_ethernet: None, disable_for_networks: None, families: None, dns_log_until: DnsLogUntil(None), gateway_id: None, onboarding: None, organization: None, split_config: None, fallback_domains: None, proxy_port: None, disable_connectivity_checks: None, override_api_endpoint: None, override_doh_endpoint: None, override_warp_endpoint: None, override_tunnel_mtu: None, qlog_logging: None }
2024-08-26T07:33:35.511Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: 31cb7cce-6b91-4522-ad1d-2db9e67ed0d5; Success
2024-08-26T07:33:35.511Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm="settings_changed"
Success
2024-08-26T07:33:35.512Z DEBUG main_loop: warp::warp_service: Checking for registration vs settings account mismatch reg_is_teams=false settings_is_teams=false reg_org=None settings_org=None
2024-08-26T07:33:35.512Z  INFO warp::warp_service::ipc_loop: IPC connection ended
2024-08-26T07:33:35.512Z DEBUG firewall: Firewall allow API ips api_ips=[104.16.80.230, 104.17.143.163, 2606:4700::6811:8fa3, 2606:4700::6810:50e6]
2024-08-26T07:33:35.512Z DEBUG firewall: Firewall allow managed network endpoints managed_network_endpoints=[]
2024-08-26T07:33:35.512Z  INFO firewall: Firewall starting
2024-08-26T07:33:35.517Z  WARN firewall::linux: Failed to run NFT command output=Output { status: ExitStatus(unix_wait_status(256)), stdout: "", stderr: "" }
2024-08-26T07:33:35.517Z  WARN firewall::linux: Failed to set firewall rules via stdin. Retrying using temporary file exit_code=ExitStatus(unix_wait_status(256))
2024-08-26T07:33:35.525Z ERROR firewall::linux: Failed to start firewall with exit code: exit status: 1
2024-08-26T07:33:35.525Z  WARN firewall: fw.apply_rules failed e=ApplyError("nft command failed with return code: 256")
2024-08-26T07:33:35.526Z  INFO main_loop: warp::warp_service: User Settings Changed: {always_on: false->true, }
2024-08-26T07:33:35.526Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC update: SettingsUpdated
2024-08-26T07:33:35.526Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseUpdate: SettingsUpdated
2024-08-26T07:33:35.526Z DEBUG main_loop: warp::warp_service: Reconnecting on settings change
2024-08-26T07:33:35.526Z DEBUG firewall: Firewall allow API ips api_ips=[104.16.80.230, 104.17.143.163, 2606:4700::6811:8fa3, 2606:4700::6810:50e6]
2024-08-26T07:33:35.527Z DEBUG firewall: Firewall allow managed network endpoints managed_network_endpoints=[]
2024-08-26T07:33:35.527Z  INFO firewall: Firewall starting
2024-08-26T07:33:35.531Z  WARN firewall::linux: Failed to run NFT command output=Output { status: ExitStatus(unix_wait_status(256)), stdout: "", stderr: "" }
2024-08-26T07:33:35.531Z  WARN firewall::linux: Failed to set firewall rules via stdin. Retrying using temporary file exit_code=ExitStatus(unix_wait_status(256))
2024-08-26T07:33:35.537Z ERROR firewall::linux: Failed to start firewall with exit code: exit status: 1
2024-08-26T07:33:35.537Z  WARN firewall: fw.apply_rules failed e=ApplyError("nft command failed with return code: 256")
2024-08-26T07:33:35.537Z  WARN main_loop: warp::warp_service: Unable to update firewall on disconnect e=ApplyError("nft command failed with return code: 256")
2024-08-26T07:33:35.537Z DEBUG main_loop: warp::warp_service: Determining disconnected reason from connectivity state net_info=IPv4: [eth0; 172.17.0.2; Ethernet]; DNS servers:;   8.8.8.8:53;   8.8.4.4:53;
 power_state=None disconnect_reason=None
2024-08-26T07:33:35.537Z  WARN main_loop: warp::warp_service: Disconnecting, but reason is unknown
2024-08-26T07:33:35.537Z DEBUG firewall: Firewall allow API ips api_ips=[104.16.80.230, 104.17.143.163, 2606:4700::6811:8fa3, 2606:4700::6810:50e6]
2024-08-26T07:33:35.538Z DEBUG firewall: Firewall allow managed network endpoints managed_network_endpoints=[]
2024-08-26T07:33:35.538Z  INFO firewall: Firewall starting
2024-08-26T07:33:35.541Z  WARN firewall::linux: Failed to run NFT command output=Output { status: ExitStatus(unix_wait_status(256)), stdout: "", stderr: "" }
2024-08-26T07:33:35.541Z  WARN firewall::linux: Failed to set firewall rules via stdin. Retrying using temporary file exit_code=ExitStatus(unix_wait_status(256))
2024-08-26T07:33:35.546Z ERROR firewall::linux: Failed to start firewall with exit code: exit status: 1
2024-08-26T07:33:35.546Z  WARN firewall: fw.apply_rules failed e=ApplyError("nft command failed with return code: 256")
2024-08-26T07:33:35.546Z DEBUG firewall: Firewall allow API ips api_ips=[104.16.80.230, 104.17.143.163, 2606:4700::6811:8fa3, 2606:4700::6810:50e6]
2024-08-26T07:33:35.546Z DEBUG firewall: Firewall allow managed network endpoints managed_network_endpoints=[]
2024-08-26T07:33:35.546Z  INFO firewall: Firewall starting
2024-08-26T07:33:35.549Z  WARN firewall::linux: Failed to run NFT command output=Output { status: ExitStatus(unix_wait_status(256)), stdout: "", stderr: "" }
2024-08-26T07:33:35.549Z  WARN firewall::linux: Failed to set firewall rules via stdin. Retrying using temporary file exit_code=ExitStatus(unix_wait_status(256))
2024-08-26T07:33:35.556Z ERROR firewall::linux: Failed to start firewall with exit code: exit status: 1
2024-08-26T07:33:35.556Z  WARN firewall: fw.apply_rules failed e=ApplyError("nft command failed with return code: 256")
2024-08-26T07:33:35.557Z  WARN main_loop: warp::warp_service: Unable to update firewall on disconnect e=ApplyError("nft command failed with return code: 256")
2024-08-26T07:33:35.557Z DEBUG main_loop: warp::warp_service: Determining disconnected reason from connectivity state net_info=IPv4: [eth0; 172.17.0.2; Ethernet]; DNS servers:;   8.8.8.8:53;   8.8.4.4:53;
 power_state=None disconnect_reason=None
2024-08-26T07:33:35.557Z  WARN main_loop: warp::warp_service: Disconnecting, but reason is unknown
2024-08-26T07:33:35.557Z  WARN main_loop: warp::warp_service: Reconnect on settings change failed error=FirewallUpdateFailed(ApplyError("nft command failed with return code: 256"))
2024/08/26 07:33:36 route.go:695: auto://:1080 on [::]:1080
2024-08-26T07:33:36.816Z  WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
2024-08-26T07:33:40.817Z  WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug

Here is the full log when I run the container

warp@48c325a9010a:/app/rss$ ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 114 Aug 26 07:33 /etc/resolv.conf
warp@48c325a9010a:/app/rss$ cat /etc/resolv.conf'
search 51ur3jppi0eupdptvsj42kdvgc.bx.internal.cloudapp.net
options ndots:0
nameserver 8.8.8.8
nameserver  8.8.4.4

here is the output of resolv.conf
This container is run locally

@cmj2002
Copy link
Owner

cmj2002 commented Aug 26, 2024

The No comment line contained an owner slug might means the line # This file was generated by cloudflare-warp. missing, which may indicates that WARP failed to edit lsattr /etc/resolv.conf.

What's the output of lsattr /etc/resolv.conf? Since you must have been edit the dockerfile and entrypoint, did you start the warp-svc by root (or using sudo)?

@pohfow
Copy link
Author

pohfow commented Aug 26, 2024

---------------------- /etc/resolv.conf
is the output of lsattr /etc/resolv.conf

I have also tried to run the docker image caomingjun/warp as is without any modifications to its Dockerfile or Entrypoint.
I used the command docker run caomingjun/warp and it gives this error WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug. The testing was done locally

@cmj2002
Copy link
Owner

cmj2002 commented Aug 26, 2024

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).

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 resolv.conf warning also appeared, while my container is running normally, indicating that the issue with the container is unrelated to resolv.conf.

I found nft errors in your log, this might be a nft problem.

2024-08-26T07:33:35.537Z DEBUG firewall: Firewall allow API ips api_ips=[104.16.80.230, 104.17.143.163, 2606:4700::6811:8fa3, 2606:4700::6810:50e6]
2024-08-26T07:33:35.538Z DEBUG firewall: Firewall allow managed network endpoints managed_network_endpoints=[]
2024-08-26T07:33:35.538Z  INFO firewall: Firewall starting
2024-08-26T07:33:35.541Z  WARN firewall::linux: Failed to run NFT command output=Output { status: ExitStatus(unix_wait_status(256)), stdout: "", stderr: "" }
2024-08-26T07:33:35.541Z  WARN firewall::linux: Failed to set firewall rules via stdin. Retrying using temporary file exit_code=ExitStatus(unix_wait_status(256))
2024-08-26T07:33:35.546Z ERROR firewall::linux: Failed to start firewall with exit code: exit status: 1
2024-08-26T07:33:35.546Z  WARN firewall: fw.apply_rules failed e=ApplyError("nft command failed with return code: 256")

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)

@pohfow
Copy link
Author

pohfow commented Sep 13, 2024

Accept Terms of Service and Privacy Policy?

Modified warp to use local proxy but cannot get past this.

also tried adding --accept-tos

@cmj2002
Copy link
Owner

cmj2002 commented Sep 13, 2024

Accept Terms of Service and Privacy Policy?

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 --accept-tos when starting the daemon warp-svc and running warp-cli connect, you may need to add that parameter elsewhere, depending on how your Dockerfile is written and at what point during the container's execution it prompts for TOS acceptance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cmj2002 @pohfow