FRR can't allocate memory

[Aperence]

Hello,
While trying to run one of the example lab, I encounter always the same error "fork() can't allocate memory" while trying to run /etc/init.d/frr start.

Although, when checking the memory allowed to each device, I can see that they each have 15GB available, which should be more than enough to run frr.

I thus wonder what am I doing wrong ?
Thanks in advance for you help !

NB : my computer is running on fedora 38

[tcaiazzi]

Hi @Aperence,

Thanks for opening the issue!

To debug the problem I need further information:

• What is your Docker version?
• Do you have the last version of Kathará?

Thanks,
Tommaso

[Aperence]

Hi,

• My current docker version is 24.0.5 (see screen below for more details)
  

• I indeed have the latest version of kathara as I installed it 3 days ago (3.6.3)

Thanks already for your help

[tcaiazzi]

Hi @Aperence,

Sorry for the delay, I was on vacation until yesterday 😇

I'm also experiencing your issue on my Fedora 38 VM.

This is a very strange behavior since the error happens only with frr. All the other daemons such as quagga, bind, apache2 work fine.

Moreover, I found that if you use the su command, then `frr' starts correctly.

I think there is some differences in the environment of the two scenarios, and for some reason using su something (that allows frr to run properly) changes.

I'm still searching for a proper explanation. If you have some ideas let me know!

Thanks!

[Aperence]

Hi,

Hope you had a good holiday !

This behaviour seems indeed really strange, and I don't really know what could be the cause of it, sadly. I'll inform you if I find any reason in the future, but it seems complicated

At least, thanks to your discovery with su, I can temporarily make a work-around by using:

su <<EOF
/etc/init.d/frr start
EOF

This isn't ideal, but well it kinda works for the moment at least 🙂

[lorenzo93]

Hi everyone,

@BuonHobo find the same bug in ArchLinux.
With the new Docker Images the init.d folder has been deprecated, so you need to use systemctl.
The new workaround for systemctl is:

su -c "systemctl start frr"

[tcaiazzi]

Hi @Aperence,

I'm closing this issue, since I opened a new one (KatharaFramework/Docker-Images#10) in the Docker images repository. We can continue the discussion there.

Many thanks for the help and support 🚀