Bug #5362
open
Compatability issues with Mininet in 24.04.2
Added by Alexander Lane 21 days ago.
Updated 20 days ago.
Description
The Mininet package and its dependencies are currently throwing errors with our default install script on a fresh 24.04.2 image. Given that no PR has been merged to any of their managed projects despite people submitting fixes in nearly 2 years, we may need to discuss forking Mininet formally in the future, as well as accelerating providing Vagrant images in the shorter term.
Related issues
1 (1 open — 0 closed)
Davide Pesavento wrote in #note-1:
What are the errors?
- Mininet is reliant on the pep8 package; this was renamed to pycodestyle nearly a decade ago, but I suspect whatever compatability support is no longer extant.
- If we modify the Mininet package to use this instead, we next get error: externally managed environment due to it trying to use pip from the system Python 3 distro. There's not really obvious existing support for running in a Python environment, even if this is probably a feature we should aim to support.
- If we temporarily force Python to allow us to use pip on the system's Python3, Mininet's fork of OpenFlow crashes due to attempting to redefine srtlcpy. Openflow also throws a large number of warning at compile time.
- setup.py throws a number of messages about it being deprecated by the devs (https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html), this is on both our and Mininet's ends. This does not prevent installation.
Seemingly we can run an experiment after all this. But this is too many steps for an end user and requires too much intervention and potential OS breaking outside of a VM image distribution.
- Related to Task #5363: Investigate swapping to Containernet added
Also available in: Atom
PDF