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
We’re trying to run Prefect natively on the OT-2 for workflow orchestration. However, we ran into compatibility issues because the robot’s glibc version is 2.25, while Prefect‘s dependencies require 2.28+.
ldd --version
ldd (GNU libc) 2.25
$Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$Written by Roland McGrath and Ulrich Drepper.
Would it be possible to include a more recent version of glibc in future releases? Alternatively, is there a safe way for us to upgrade it on our side?
Acceptance criteria
No response
The text was updated successfully, but these errors were encountered:
Neil-YL
added
the
feature-request
A request for a new feature or a change that isn't a bug. May require further triage or scoping.
label
Apr 25, 2025
There's not really a safe way for you to upgrade the glibc version for the robot as a whole. What you could do is get an appropriately compiled glibc version, drop it in locally, and then run prefect with an LD_PRELOAD that points to it.
Compiling it appropriately will be a bit of a pain but you might be able to get it from a recent raspbian release that supports the rpi3b; glibc is nice and stable and so you could put it on a pi and copy it from /lib (or just flash it to an sd card and browse the sd card from a linux machine).
Overview
We’re trying to run Prefect natively on the OT-2 for workflow orchestration. However, we ran into compatibility issues because the robot’s glibc version is 2.25, while Prefect‘s dependencies require 2.28+.
Implementation details
For more details I have opened an issue on package request.
Design
Would it be possible to include a more recent version of glibc in future releases? Alternatively, is there a safe way for us to upgrade it on our side?
Acceptance criteria
No response
The text was updated successfully, but these errors were encountered: