search

cmj2002 / warp-docker

Run Cloudflare WARP in Docker.
GNU General Public License v3.0
317 stars 101 forks source link

arm64版本 #6

Closed XavierPENROSE closed 1 year ago

XavierPENROSE commented 1 year ago

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

cmj2002 commented 1 year ago

Cloudflare WARP 客户端似乎并不支持 arm64。社区讨论过该话题，Cloudflare 团队成员称他们有一个内部 ticket 跟踪该问题。但是至今它尚未完成，我的构建日志显示：

N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://pkg.cloudflareclient.com jammy InRelease' doesn't support architecture 'arm64'

如果哪一天他们支持了 arm64 ，你可以随时重新打开该 issue。

XavierPENROSE commented 1 year ago

好的，非常感谢。

在 2023年9月24日星期日，Cao Mingjun @.***> 写道：

Cloudflare WARP 客户端似乎并不支持 arm64。社区讨论 https://community.cloudflare.com/t/cloudflare-warp-linux-client-for-armv8-arm64-aarch64-devices/278777过该话题，Cloudflare 团队成员称他们有一个内部 ticket 跟踪该问题。但是至今它尚未完成，我的构建日志显示：

N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://pkg.cloudflareclient.com jammy InRelease' doesn't support architecture 'arm64'

如果哪一天他们支持了 arm64 ，你可以随时重新打开该 issue。

— Reply to this email directly, view it on GitHub https://github.com/cmj2002/warp-docker/issues/6#issuecomment-1732351547, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG5QK5PIBHU37WBMEML6MYLX34DCDANCNFSM6AAAAAA5EIRJHM . You are receiving this because you authored the thread.Message ID: @.***>

XavierPENROSE commented 1 year ago

大佬您好，我今天尝试了一下通过aptman/qus在arm64上运行这个镜像，容器可以正常部署，但是运行的时候遇到了问题，能否帮忙看一下是哪里有问题，非常感谢，运行日志如下： stdout: [2m2023-09-24T08:09:36.598Z[0m [32m INFO[0m [2mwarp::warp_service[0m[2m:[0m Starting WarpService [3mpid[0m[2m=[0m17 stdout: [2m2023-09-24T08:09:36.635Z[0m [32m INFO[0m [2mwarp::warp_service[0m[2m:[0m Version: 2023.7.40 stdout: [2m2023-09-24T08:09:36.751Z[0m [34mDEBUG[0m [2mwarp_settings::raw_settings[0m[2m:[0m Loading settings from file "/var/lib/cloudflare-warp/settings.json" stdout: [2m2023-09-24T08:09:36.784Z[0m [32m INFO[0m [2mwarp_settings::manager[0m[2m:[0m User preferences not loaded [3me[0m[2m=[0mNo such file or directory (os error 2) stdout: [2m2023-09-24T08:09:36.816Z[0m [34mDEBUG[0m [2mwarp_settings::manager[0m[2m:[0m Starting local policy file watch [3mparent_path[0m[2m=[0m"/var/lib/cloudflare-warp" stdout: [2m2023-09-24T08:09:37.049Z[0m [34mDEBUG[0m [1mwatchdog[0m[2m:[0m [2mwarp::watchdog[0m[2m:[0m Kicking off watchdog stdout: [2m2023-09-24T08:09:37.085Z[0m [32m INFO[0m [1mmain_loop[0m[2m:[0m [2mwarp_net::ipc[0m[2m:[0m Bound ipc socket [3mname[0m[2m=[0m"cloudflare-warp/warp_service" [3mpath[0m[2m=[0m"/run/cloudflare-warp/warp_service" stdout: [2m2023-09-24T08:09:37.094Z[0m [32m INFO[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service[0m[2m:[0m Warp IPC listening on "cloudflare-warp/warp_service" stdout: [2m2023-09-24T08:09:37.151Z[0m [33m WARN[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service[0m[2m:[0m Failed to load Registration [3merror[0m[2m=[0mOsError(Os { code: 2, kind: NotFound, message: "No such file or directory" }) stdout: [2m2023-09-24T08:09:38.088Z[0m [33m WARN[0m [1mwatchdog[0m[2m:[0m [2mwarp::watchdog[0m[2m:[0m Watchdog reports hung daemon [3mwatchdog_name[0m[2m=[0m"main loop" [3mhang_count[0m[2m=[0m1 [3mhang_tick[0m[2m=[0m1 stdout: [2m2023-09-24T08:09:38.234Z[0m [34mDEBUG[0m [2mwarp_api::addresses[0m[2m:[0m Caching initial API IPs [3mconsumer[0m[2m=[0m[104.19.237.24, 104.19.236.24, 2606:4700:d0::a29f:c001] [3mteams[0m[2m=[0m[162.159.137.105, 162.159.138.105, 2606:4700:7::a29f:8969] stdout: [2m2023-09-24T08:09:38.254Z[0m [34mDEBUG[0m [2mwarp::warp_api[0m[2m:[0m Sending API request GET api.cloudflareclient.com./v0/client_config stdout: [2m2023-09-24T08:09:38.307Z[0m [34mDEBUG[0m [1mnew[0m[1m{[0mhostname="api.cloudflareclient.com." resolve_ips=[104.19.237.24, 104.19.236.24, 2606:4700:d0::a29f:c001][1m}[0m[2m:[0m [2mwarp_api::unauthenticated[0m[2m:[0m close [3mtime.busy[0m[2m=[0m44.4ms [3mtime.idle[0m[2m=[0m3.46ms stdout: [2m2023-09-24T08:09:38.405Z[0m [34mDEBUG[0m [2mwarp::warp_api[0m[2m:[0m Sending API request GET zero-trust-client.cloudflareclient.com./v0/client_config stdout: [2m2023-09-24T08:09:38.411Z[0m [34mDEBUG[0m [1mnew[0m[1m{[0mhostname="zero-trust-client.cloudflareclient.com." resolve_ips=[162.159.137.105, 162.159.138.105, 2606:4700:7::a29f:8969][1m}[0m[2m:[0m [2mwarp_api::unauthenticated[0m[2m:[0m close [3mtime.busy[0m[2m=[0m4.19ms [3mtime.idle[0m[2m=[0m270µs stdout: [2m2023-09-24T08:09:39.091Z[0m [33m WARN[0m [1mwatchdog[0m[2m:[0m [2mwarp::watchdog[0m[2m:[0m Watchdog reports hung daemon [3mwatchdog_name[0m[2m=[0m"main loop" [3mhang_count[0m[2m=[0m1 [3mhang_tick[0m[2m=[0m2 stdout: [2m2023-09-24T08:09:39.205Z[0m [34mDEBUG[0m [1mrun[0m[2m:[0m [2mwarp_settings::manager[0m[2m:[0m 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: [] }) }) stdout: [2m2023-09-24T08:09:39.242Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service[0m[2m:[0m Checking for registration vs settings account mismatch [3mreg_is_teams[0m[2m=[0mfalse [3msettings_is_teams[0m[2m=[0mfalse [3mreg_org[0m[2m=[0mNone [3msettings_org[0m[2m=[0mNone stdout: [2m2023-09-24T08:09:39.251Z[0m [32m INFO[0m [1mmain_loop[0m[2m:[0m [2mfirewall[0m[2m:[0m Firewall stopped stdout: [2m2023-09-24T08:09:39.253Z[0m [32m INFO[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service[0m[2m:[0m New User Settings stdout: [2m2023-09-24T08:09:39.255Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Sending IPC update: SettingsUpdated stdout: [2m2023-09-24T08:09:39.258Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Ipc Broadcast ResponseUpdate: SettingsUpdated stdout: [2m2023-09-24T08:09:39.260Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service[0m[2m:[0m update_settings: no restart required stdout: [2m2023-09-24T08:09:39.293Z[0m [32m INFO[0m [2mwarp::warp_service[0m[2m:[0m Spawning registration changed IPC loop stdout: [2m2023-09-24T08:09:39.319Z[0m [32m INFO[0m [2mwarp::warp_service::ipc_loop[0m[2m:[0m IPC: new connection [3mprivileged[0m[2m=[0mtrue [3mprocess_name[0m[2m=[0m"/bin/qemu-x86_64-static (deleted)" [3mpid[0m[2m=[0m37 stdout: [2m2023-09-24T08:09:39.355Z[0m [34mDEBUG[0m [1mnew[0m[1m{[0mhostname="api.cloudflareclient.com." resolve_ips=[104.19.237.24, 104.19.236.24, 2606:4700:d0::a29f:c001][1m}[0m[2m:[0m [2mwarp_api::unauthenticated[0m[2m:[0m close [3mtime.busy[0m[2m=[0m5.85ms [3mtime.idle[0m[2m=[0m386µs stdout: [2m2023-09-24T08:09:39.462Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service[0m[2m:[0m Entering main loop arm [3marm[0m[2m=[0m"settings_changed" stdout: [2m2023-09-24T08:09:39.468Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service[0m[2m:[0m Checking for registration vs settings account mismatch [3mreg_is_teams[0m[2m=[0mfalse [3msettings_is_teams[0m[2m=[0mfalse [3mreg_org[0m[2m=[0mNone [3msettings_org[0m[2m=[0mNone stdout: [2m2023-09-24T08:09:39.470Z[0m [32m INFO[0m [1mmain_loop[0m[2m:[0m [2mfirewall[0m[2m:[0m Firewall stopped stdout: [2m2023-09-24T08:09:39.471Z[0m [32m INFO[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service[0m[2m:[0m New User Settings stdout: [2m2023-09-24T08:09:39.473Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Sending IPC update: SettingsUpdated stdout: [2m2023-09-24T08:09:39.474Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Ipc Broadcast ResponseUpdate: SettingsUpdated stdout: [2m2023-09-24T08:09:39.493Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service[0m[2m:[0m update_settings: no restart required stdout: [2m2023-09-24T08:09:39.537Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Ipc request: eafc74fc-640d-43f2-be8b-6dcf0ed42127; GetAppSettings stdout: [2m2023-09-24T08:09:39.705Z[0m [34mDEBUG[0m [2mwarp_api::unauthenticated[0m[2m:[0m Sending crash report: [3mreport.source[0m[2m=[0mDaemon stdout: [2m2023-09-24T08:09:40.163Z[0m [34mDEBUG[0m [2msentry-ignore[0m[2m:[0m Serialized panic [3mreport_path[0m[2m=[0m"/var/lib/cloudflare-warp/crash_reports/daemon_1695542980153186708.json" [3mid[0m[2m=[0m98dc4b6c-067a-4738-8c16-2cee236ab305 stdout: [2m2023-09-24T08:09:40.191Z[0m [31mERROR[0m [2msentry-ignore[0m[2m:[0m panicked at 'route_change stream closed: Os { code: 22, kind: InvalidInput, message: "Invalid argument" }', /w/1/s/warp/src/warp_service/network_change.rs:108:37 [3mpanic.file[0m[2m=[0m"/w/1/s/warp/src/warp_service/network_change.rs" [3mpanic.line[0m[2m=[0m108 [3mpanic.column[0m[2m=[0m37 [3mbacktrace[0m[2m=[0m 0: logger::panic_hook::set_panic_hook::{{closure}} stdout: 1: std::panicking::rust_panic_with_hook stdout: 2: std::panicking::begin_panic_handler::{{closure}} stdout: 3: std::sys_common::backtrace::rust_end_short_backtrace stdout: 4: rust_begin_unwind stdout: 5: core::panicking::panic_fmt stdout: 6: core::result::unwrap_failed stdout: 7: <tracing::instrument::Instrumented as core::future::future::Future>::poll stdout: 8: tokio::loom::std::unsafe_cell::UnsafeCell::with_mut stdout: 9: tokio::runtime::task::harness::Harness<T,S>::poll stdout: 10: tokio::task::local::LocalSet::tick stdout: 11: <tokio::task::local::RunUntil as core::future::future::Future>::poll stdout: 12: <tracing::instrument::Instrumented as core::future::future::Future>::poll stdout: 13: tokio::runtime::park::CachedParkThread::block_on stdout: 14: tokio::runtime::scheduler::multi_thread::MultiThread::block_on stdout: 15: tokio::runtime::runtime::Runtime::block_on stdout: 16: warp_svc::main stdout: 17: std::sys_common::backtrace::rust_begin_short_backtrace stdout: 18: std::rt::lang_start::{{closure}} stdout: 19: std::rt::lang_start_internal stdout: 20: main stdout: 21: stdout: 22: libc_start_main stdout: 23: _start stdout: stdout: [2m2023-09-24T08:09:40.234Z[0m [31mERROR[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service[0m[2m:[0m Critical task unexpectedly stopped: Some(("Network/Route changes", Err(JoinError::Panic(Id(32), ...)))) stdout: [2m2023-09-24T08:09:40.259Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2msentry-ignore[0m[2m:[0m Serialized panic [3mreport_path[0m[2m=[0m"/var/lib/cloudflare-warp/crash_reports/daemon_1695542980253408692.json" [3mid[0m[2m=[0m05d815da-fd87-4b49-a4a9-bec339778d6e stdout: [2m2023-09-24T08:09:40.263Z[0m [31mERROR[0m [1mmain_loop[0m[2m:[0m [2msentry-ignore[0m[2m:[0m panicked at 'Critical task unexpectedly stopped: Some(("Network/Route changes", Err(JoinError::Panic(Id(32), ...))))', /__w/1/s/warp/src/warp_service.rs:746:21 [3mpanic.file[0m[2m=[0m"/w/1/s/warp/src/warp_service.rs" [3mpanic.line[0m[2m=[0m746 [3mpanic.column[0m[2m=[0m21 [3mbacktrace[0m[2m=[0m 0: logger::panic_hook::set_panic_hook::{{closure}} stdout: 1: std::panicking::rust_panic_with_hook stdout: 2: std::panicking::begin_panic_handler::{{closure}} stdout: 3: std::sys_common::backtrace::__rust_end_short_backtrace stdout: 4: rust_begin_unwind stdout: 5: core::panicking::panic_fmt stdout: 6: warp::warp_service::WarpService::main_loop::{{closure}}::{{closure}} stdout: 7: warp::warp_service::WarpService::start::{{closure}} stdout: 8: <tokio::task::local::RunUntil as core::future::future::Future>::poll stdout: 9: <tracing::instrument::Instrumented as core::future::future::Future>::poll stdout: 10: tokio::runtime::park::CachedParkThread::block_on stdout: 11: tokio::runtime::scheduler::multi_thread::MultiThread::block_on stdout: 12: tokio::runtime::runtime::Runtime::block_on stdout: 13: warp_svc::main stdout: 14: std::sys_common::backtrace::rust_begin_short_backtrace stdout: 15: std::rt::lang_start::{{closure}} stdout: 16: std::rt::lang_start_internal stdout: 17: main stdout: 18: stdout: 19: libc_start_main stdout: 20: _start stdout: stdout: [2m2023-09-24T08:09:40.286Z[0m [33m WARN[0m [2mwarp::warp_service::ipc_loop[0m[2m:[0m IPC failed to get response from main loop oneshot! stdout: [2m2023-09-24T08:09:40.293508Z[0m [31mERROR[0m [2mwarp_ipc::client[0m[2m:[0m Unable to find callback. This is a bug. [3mresponse[0m[2m=[0mIpcStatus(CriticalError) stdout: [2m2023-09-24T08:09:40.312Z[0m [33m WARN[0m [1mwatchdog[0m[2m:[0m [2mwarp::watchdog[0m[2m:[0m Watchdog reports that daemon has disconnected [3mwatchdog_name[0m[2m=[0m"main loop" stdout: [2m2023-09-24T08:09:40.314Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service[0m[2m:[0m close [3mtime.busy[0m[2m=[0m572ms [3mtime.idle[0m[2m=[0m2.71s stdout: [2m2023-09-24T08:09:40.315Z[0m [34mDEBUG[0m [1mwatchdog[0m[2m:[0m [2mwarp::watchdog[0m[2m:[0m close [3mtime.busy[0m[2m=[0m3.28s [3mtime.idle[0m[2m=[0m1.63ms stdout: [2m2023-09-24T08:09:40.321Z[0m [32m INFO[0m [2mwarp::warp_service[0m[2m:[0m Dropping WarpService stdout: [2m2023-09-24T08:09:40.324Z[0m [32m INFO[0m [2mfirewall[0m[2m:[0m Firewall stopped stdout: [2m2023-09-24T08:09:40.356Z[0m [32m INFO[0m [2mwarp::warp_service::ipc_loop[0m[2m:[0m IPC connection ended

Cao Mingjun @.***> 于2023年9月24日周日 00:13写道：

Cloudflare WARP 客户端似乎并不支持 arm64。社区讨论 https://community.cloudflare.com/t/cloudflare-warp-linux-client-for-armv8-arm64-aarch64-devices/278777过该话题，Cloudflare 团队成员称他们有一个内部 ticket 跟踪该问题。但是至今它尚未完成，我的构建日志显示：

N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://pkg.cloudflareclient.com jammy InRelease' doesn't support architecture 'arm64'

如果哪一天他们支持了 arm64 ，你可以随时重新打开该 issue。

— Reply to this email directly, view it on GitHub https://github.com/cmj2002/warp-docker/issues/6#issuecomment-1732351547, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG5QK5PIBHU37WBMEML6MYLX34DCDANCNFSM6AAAAAA5EIRJHM . You are receiving this because you authored the thread.Message ID: @.***>

cmj2002 commented 1 year ago

我没有遇到过类似的问题，所以我尝试仅凭日志进行分析，我的可能是错误的。

程序在处理 Routes changed 时遇到了问题。这可能是由于 qus 下的特殊网络环境，而我 qus 完全没有了解。由于容器在 amd64 上允许正常，而在（旨在允许跨平台镜像的）qus 上报错，我认为这个应该是因为 qus 未能完全模拟 amd64 环境。我建议你在 qus 社区寻求解答。当然由于没有 warp 客户端的源代码，我觉得他们也可能比较难进行诊断，除非这源于一个已知问题。

XavierPENROSE commented 1 year ago

谢谢回答，看来目前想在arm64平台上运行官方warp还是挺难的，不管怎么样，再次感谢。

在 2023年9月24日星期日，Cao Mingjun @.***> 写道：

我没有遇到过类似的问题，所以我尝试仅凭日志进行分析，我的可能是错误的。

程序在处理 Routes changed 时遇到了问题。这可能是由于 qus 下的特殊网络环境，而我 qus 完全没有了解。由于容器在 amd64 上允许正常，而在（旨在允许跨平台镜像的）qus 上报错，我认为这个应该是因为 qus 未能完全模拟 amd64 环境。我建议你在 qus 社区寻求解答。当然由于没有 warp 客户端的源代码，我觉得他们也可能比较难进行诊断，除非这源于一个已知问题。

— Reply to this email directly, view it on GitHub https://github.com/cmj2002/warp-docker/issues/6#issuecomment-1732524115, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG5QK5M6KXJB6SJZTCDJV5DX37YURANCNFSM6AAAAAA5EIRJHM . You are receiving this because you authored the thread.Message ID: @.***>