Luap99
commented
10 months ago see https://github.com/containers/podman/issues/16194, you should try using a newer netavark which should contain a new sha2 code which caused this problem
Closed andrico21 closed 10 months ago
Luap99
commented
10 months ago see https://github.com/containers/podman/issues/16194, you should try using a newer netavark which should contain a new sha2 code which caused this problem
andrico21
commented
10 months ago just to make this issue more informative for future - added stack:
#0 0x000055b8c8d863cb in _ZN4sha26sha5123x8627sha512_compress_x86_64_avx217he658abd7db629edfE.llvm.10846658284507516593 ()
#1 0x000055b8c8c71c79 in netavark::network::core_utils::CoreUtils::create_network_hash ()
#2 0x000055b8c8c6fa04 in netavark::network::bridge::Bridge::get_firewall_conf ()
#3 0x000055b8c8c6d2b6 in <netavark::network::bridge::Bridge as netavark::network::driver::NetworkDriver>::setup ()
#4 0x000055b8c8d180e7 in netavark::commands::setup::Setup::exec ()
#5 0x000055b8c8bf782c in netavark::main ()
#6 0x000055b8c8bfa5f3 in std::sys_common::backtrace::__rust_begin_short_backtrace ()
#7 0x000055b8c8bf7f09 in _ZN3std2rt10lang_start28_$u7b$$u7b$closure$u7d$$u7d$17hea9e91d4d6771513E.llvm.10229266140333461407 ()
#8 0x000055b8c8ff6281 in core::ops::function::impls::{impl#2}::call_once<(), (dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe)> (self=..., args=<optimized out>) at /build/rustc-ZOqcvC/rustc-1.61.0+dfsg1/library/core/src/ops/function.rs:259
#9 std::panicking::try::do_call<&(dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe), i32> (data=<optimized out>) at library/std/src/panicking.rs:492
#10 std::panicking::try<i32, &(dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe)> (f=...) at library/std/src/panicking.rs:456
#11 std::panic::catch_unwind<&(dyn core::ops::function::Fn<(), Output=i32> + core::marker::Sync + core::panic::unwind_safe::RefUnwindSafe), i32> (f=...) at library/std/src/panic.rs:137
#12 std::rt::lang_start_internal::{closure#2} () at library/std/src/rt.rs:128
#13 std::panicking::try::do_call<std::rt::lang_start_internal::{closure_env#2}, isize> (data=<optimized out>) at library/std/src/panicking.rs:492
#14 std::panicking::try<isize, std::rt::lang_start_internal::{closure_env#2}> (f=...) at library/std/src/panicking.rs:456
#15 std::panic::catch_unwind<std::rt::lang_start_internal::{closure_env#2}, isize> (f=...) at library/std/src/panic.rs:137
#16 std::rt::lang_start_internal (main=..., argc=<optimized out>, argv=<optimized out>) at library/std/src/rt.rs:128
#17 0x000055b8c8bf7ef2 in main ()
Issue Description
Fresh installation of Ubuntu 23.10 (22.04 with Kubic repo gives absolutely the same behavior) with 'podman' package installed. Unable to run any rootful-containers and getting netavark EOF message. Rootless runs fine.
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
root@pdlab2:~# podman run -d --name dummy-httpd docker.io/library/httpd Error: netavark: : EOF
root@pdlab2:~# podman run --log-level debug -d docker.io/library/httpd
Describe the results you expected
Rootful container up and running.
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
kvm/qemu based VM
podman version
dpkg --status podman
Additional information
It works for rootless, but I'm unable to run classic rootful-container.
root@pdlab2:~# dmesg --clear; podman run -d docker.io/library/httpd; dmesg