Closed clansty closed 2 months ago
The built container unable to run and shows Error: unable to start daemon - paths must not contain interior null bytes
without any backtrace. I think we need to debug the rust code
Stack backtrace:
0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
1: proxmox_rest_server::command_socket::CommandSocket::spawn
2: proxmox_backup_api::run::{{closure}}::{{closure}}
3: tokio::runtime::context::runtime::enter_runtime
4: tokio::runtime::runtime::Runtime::block_on
5: proxmox_async::runtime::main
6: proxmox_backup_api::main
7: std::sys_common::backtrace::__rust_begin_short_backtrace
8: std::rt::lang_start::{{closure}}
9: std::rt::lang_start_internal
10: main
11: <unknown>
12: __libc_start_main
13: _start
Solved!
please merge this one
This PR add support for PBS v3.2.7
Tested build on x86_64
The following changes has been made, the progress cost me >5 hours:
.cargo/config
file has been renamed to.cargo/config.toml
so we should add new filename tostrip-cargo.bash
proxmox-perl-rs/pve-rs
not run, and has been removed by a new patchproxmox-perl-rs/pve-rs
adds dependences of libproxmox-rs-perl to loadProxmox::Lib::SslProbe
needed for the test. But this leads to circular dependency. It's safe to remove the dependencyproxmox-backup
, the Debian's cargo wrapper explainsdebian/cargo_home/config
not found, and added a-Zavoid-dev-deps
which is nightly feature to the real cargo, but did nothing good. So I replaced it with the real cargotarget
dir fromtarget/$(DEB_HOST_RUST_TYPE)/release
totarget/release
so I manually added an arg to cargo to definetarget
dir. Generation of docs and some tests depends on it