Go 1.22.0 triggers glibc bug affecting SingularityCE on Ubuntu 20.04 / Debian 10

49 views
Skip to first unread message

David Trudgian

unread,
Feb 26, 2024, 3:32:12 AM2/26/24
to Singularity Community Edition
All,

When SingularityCE is built with Go 1.22.0, on at least Ubuntu 20.04, Debian 10, and perhaps other distributions, the resulting binary may fail to launch containers. A SIGSEV error will occur.

This is caused by a change in Go 1.22.0 triggering a bug in glibc.

The issue affects other runtimes, e.g. runc and incus.

At this time, please build SingularityCE with the latest Go 1.21.x release to avoid the issue on Ubuntu 20.04 and Debian 10.

An issue to track the problem has been opened on the SingularityCE repo here:


More context is available in the runc issue tracker, and the Go issue tracker:


Cheers,

DT




David Trudgian

unread,
Jun 5, 2024, 9:31:12 AM6/5/24
to Singularity Community Edition
All,

The issue which caused SingularityCE to crash when using a PID namespace on Ubuntu 20.04 / Debian 10, if compiled with Go 1.22, has been resolved with the Go 1.22.4 release.

Please use Go 1.22.4 or greater, or Go 1.21 to compile SingularityCE.

Cheers,

DT
Reply all
Reply to author
Forward
0 new messages