You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I have a few standalone containers running under podman, using a macvlan network to make them available to an internal LAN network. I'm observing the following:
1: Every time the external router assigns a DHCP host configuration to a container, netavark logs this message:
dhcp-proxy: [ERROR netavark::commands::dhcp_proxy] no available capacity
2: Every week or so I will get a hard crash on netavark with the following logs, and the container will no longer be reachable at the static IP lease addresses:
Jul 11 21:29:36 build-00 user.notice dhcp-proxy: thread '<unnamed>' panicked at library/std/src/sys/pal/unix/stack_overflow.rs:158:13:
Jul 11 21:29:36 build-00 user.notice dhcp-proxy: failed to set up alternative stack guard page: Out of memory (os error 12)
Jul 11 21:29:36 build-00 user.notice dhcp-proxy: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Jul 11 21:29:36 build-00 user.notice dhcp-proxy: thread '<unnamed>' panicked at library/std/src/sys/pal/unix/stack_overflow.rs:154:13:
Jul 11 21:29:36 build-00 user.notice dhcp-proxy: failed to allocate an alternative stack: Out of memory (os error 12)
Jul 11 21:29:36 build-00 daemon.err /etc/init.d/netavark-dhcp-proxy[38874]: start-stop-daemon: failed to start `/usr/libexec/podman/netavark'
Jul 11 21:29:36 build-00 user.notice dhcp-proxy: * start-stop-daemon: failed to start `/usr/libexec/podman/netavark'
I just tried building and upgrading to the latest upstream version of netavark, but I'm seeing the same log messages. I'll wait to see if I get a crash with this version.
Hi, I have a few standalone containers running under podman, using a
macvlan
network to make them available to an internal LAN network. I'm observing the following:1: Every time the external router assigns a DHCP host configuration to a container,
netavark
logs this message:2: Every week or so I will get a hard crash on
netavark
with the following logs, and the container will no longer be reachable at the static IP lease addresses:I just tried building and upgrading to the latest upstream version of
netavark
, but I'm seeing the same log messages. I'll wait to see if I get a crash with this version.Let me know if more info is needed. Thanks!
The text was updated successfully, but these errors were encountered: