Letsencrypt docker image not starting with cryptical python error

So I think there was a problem before with some security modules complaining about self-modifying code and the interface that Python uses to load OpenSSL (which effectively uses self-modifying code, akin to a JIT). I haven’t been able to find the earlier forum threads about this and I don’t remember the details. Do you know which particular Linux security tools the Alpine “hardened” image incorporates?

2 Likes