Page 1 of 1
Support Arista cEOS 4.32+ in Docker
Posted: Wed Jan 29, 2025 5:34 pm
by nickolas
Arista EOS (all variants) switched off CentOS to ALMA Linux in 4.32.x. When I try to follow the steps to have cEOS built as a docker.io image for use in EVE-NG Pro 6.2.0-20 the node will not stay running for more than 4 secs. When I try cEOS images below 4.32.x the Image will start and telnet console access goes to the Linux root cli, but when starting the Cli for the EOS shell, it can't find sysdb and starts in Standalone mode.
Arista points out that cEOS works in ContainerLab and GNS3, and I thought GNS3 was a predecessor to EVE-NG. So I am asking that cEOS on ALMA (Versions 4.32 and up) be looked at for operation as a Docker.io container model to permit larger node counts that QEMU supports.
Re: Support Arista cEOS 4.32+ in Docker
Posted: Wed Jan 29, 2025 8:55 pm
by rusty725
which steps are you following ?
Re: Support Arista cEOS 4.32+ in Docker
Posted: Fri Jan 09, 2026 6:22 am
by max1987martin
nickolas wrote: ↑Wed Jan 29, 2025 5:34 pm
Arista EOS (all variants) switched off CentOS to ALMA Linux in 4.32.x. When I try to follow the steps to have cEOS built as a docker.io image for use in EVE-NG Pro 6.2.0-20 the node will not stay running for more than 4 secs. When I try cEOS images below 4.32.x the Image will start and telnet console access goes to the Linux root cli, but when starting the Cli for the EOS shell, it can't find sysdb and starts in Standalone mode.
Arista points out that cEOS works in ContainerLab and GNS3, and I thought GNS3 was a predecessor to EVE-NG. So I am asking that cEOS on ALMA (Versions 4.32 and up) be looked at for operation as a Docker.io container model to permit larger node counts that QEMU supports.
mcdvoice
Hi,
You’re running into two different (but related) issues with cEOS on EVE-NG, and unfortunately one of them is a hard architectural limitation, not a simple config bug.
cEOS 4.32+ cannot run as a Docker container in EVE-NG.
From 4.32 onward Arista moved cEOS to AlmaLinux + systemd, which requires kernel features (systemd, cgroup v2, IPC handling) that EVE-NG’s Docker engine does not support. This is why the container exits after a few seconds.
Older cEOS (<4.32) starts but fails to find sysdb because EVE-NG’s Docker runtime does not fully expose the required shared memory and namespaces.
This is a platform limitation, not a build issue. Supporting cEOS 4.32+ in EVE-NG Docker would require major changes to EVE-NG itself.