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
libsodium requires some "randomness" at startup - if not enough entropy is available from /dev/randomit hangs.
In containers there can be little sources for entropy. As described in the docs of libsodium, one workaround is to install the rng-tools (here some docs on what those do).
Would that be considered as an addition to the herokuish Dockerfiles?
If yes, happy to make a PR if you let me know where this should go.
P.S. libsodium is used e.g. in libzmq => pyzmq => jupyter, i.e. this affects anyone wanting to run jupyter notebooks via voila apps which would randomly hang in herokuish containers.
Does heroku have that? My concern is moving too far away from their base offering. Not opposed to it, just want to be careful of how we differ so that folks don't get the wrong idea.
Additionally, I wonder if this is something that would impact cloud native buildpacks, which are the future of buildpacks in general. Would be great if you can inquire in that community slack about this as well.
libsodium
requires some "randomness" at startup - if not enough entropy is available from/dev/random
it hangs.In containers there can be little sources for entropy. As described in the docs of libsodium, one workaround is to install the
rng-tools
(here somedocs
on what those do).Would that be considered as an addition to the herokuish Dockerfiles?
If yes, happy to make a PR if you let me know where this should go.
P.S.
libsodium
is used e.g. inlibzmq
=>pyzmq
=>jupyter
, i.e. this affects anyone wanting to run jupyter notebooks viavoila
apps which would randomly hang in herokuish containers.Related issues
jedisct1/libsodium#933
zeromq/libzmq#3183
zeromq/pyzmq#1224 (comment)
jupyter/help#480 (comment)
The text was updated successfully, but these errors were encountered: