diff --git a/README.md b/README.md
index 6d8ac4d47ca..2cb8ed9f91e 100644
--- a/README.md
+++ b/README.md
@@ -29,6 +29,10 @@ A third party security audit was performed by Cure53, you can see the full repor
 
 `runc` only supports Linux. It must be built with Go version 1.19 or higher.
 
+NOTE: if building with Go 1.22.x, make sure to use 1.22.4 or a later version
+(see [issue #4233](https://github.com/opencontainers/runc/issues/4233) for
+more details).
+
 In order to enable seccomp support you will need to install `libseccomp` on your platform.
 > e.g. `libseccomp-devel` for CentOS, or `libseccomp-dev` for Ubuntu
 
diff --git a/libcontainer/nsenter/nsenter_go122.go b/libcontainer/nsenter/nsenter_go122.go
deleted file mode 100644
index 2b9ece0ad29..00000000000
--- a/libcontainer/nsenter/nsenter_go122.go
+++ /dev/null
@@ -1,15 +0,0 @@
-//go:build go1.22
-
-package nsenter
-
-/*
-// We know for sure that glibc has issues with pthread_self() when called from
-// Go after nsenter has run. This is likely a more general problem with how we
-// ignore the rules in signal-safety(7), and so it's possible musl will also
-// have issues, but as this is just a hotfix let's only block glibc builds.
-#include <features.h>
-#ifdef __GLIBC__
-#  error "runc does not currently work properly with Go >=1.22. See <https://github.com/opencontainers/runc/issues/4233>."
-#endif
-*/
-import "C"