The 'prosody' component refuses to start in a docker setup under Ubuntu Server 24.04.2 LTS in VMware. Error messages look like this: Error initializing module 'posix' on 'auth.meet.jitsi': /usr/share/lua/5.4/prosody/util/startup.lua:357: attempt to index a nil value (field 'main_thread') | stack traceback: | /usr/share/lua/5.4/prosody/util/startup.lua:357: in field 'shutdown' | /usr/lib/prosody/modules/mod_posix.lua:70: in local 'write_pidfile' | /usr/lib/prosody/modules/mod_posix.lua:123: in main chunk | [C]: in function 'xpcall' | /usr/share/lua/5.4/prosody/core/modulemanager.lua:270: in upvalue 'do_load_module' | /usr/share/lua/5.4/prosody/core/modulemanager.lua:353: in function 'core.modulemanager.load' | /usr/share/lua/5.4/prosody/core/modulemanager.lua:131: in function 'core.modulemanager.load_modules_for_host' | /usr/share/lua/5.4/prosody/util/events.lua:81: in function </usr/share/lua/5.4/prosody/util/events.lua:77> | (...tail calls...) | /usr/share/lua/5.4/prosody/core/hostmanager.lua:108: in function 'core.hostmanager.activate' | /usr/share/lua/5.4/prosody/core/hostmanager.lua:58: in field '?' | /usr/share/lua/5.4/prosody/util/events.lua:81: in function </usr/share/lua/5.4/prosody/util/events.lua:77> | (...tail calls...) | /usr/share/lua/5.4/prosody/util/startup.lua:428: in function 'util.startup.prepare_to_start' | /usr/share/lua/5.4/prosody/util/startup.lua:707: in function 'util.startup.prosody' | /usr/share/lua/5.4/prosody/util/async.lua:156: in upvalue 'func' | /usr/share/lua/5.4/prosody/util/async.lua:144: in function </usr/share/lua/5.4/prosody/util/async.lua:142> or: Error initializing module 'websocket' on 'meet.jitsi': /usr/lib/prosody/modules/mod_websocket.lua:47: attempt to index a nil value | stack traceback: | /usr/lib/prosody/modules/mod_websocket.lua:47: in main chunk | [C]: in function 'xpcall' | /usr/share/lua/5.4/prosody/core/modulemanager.lua:270: in upvalue 'do_load_module' | /usr/share/lua/5.4/prosody/core/modulemanager.lua:353: in function 'core.modulemanager.load' | /usr/share/lua/5.4/prosody/core/modulemanager.lua:131: in function 'core.modulemanager.load_modules_for_host' | /usr/share/lua/5.4/prosody/util/events.lua:81: in function </usr/share/lua/5.4/prosody/util/events.lua:77> | (...tail calls...) | /usr/share/lua/5.4/prosody/core/hostmanager.lua:108: in function 'core.hostmanager.activate' | /usr/share/lua/5.4/prosody/core/hostmanager.lua:58: in field '?' | /usr/share/lua/5.4/prosody/util/events.lua:81: in function </usr/share/lua/5.4/prosody/util/events.lua:77> | (...tail calls...) | /usr/share/lua/5.4/prosody/util/startup.lua:428: in function 'util.startup.prepare_to_start' | /usr/share/lua/5.4/prosody/util/startup.lua:707: in function 'util.startup.prosody' | /usr/share/lua/5.4/prosody/util/async.lua:156: in upvalue 'func' | /usr/share/lua/5.4/prosody/util/async.lua:144: in function </usr/share/lua/5.4/prosody/util/async.lua:142> This appears to be a race condition, as this does not happen always. I.e. sometimes I get four of those messages, on the next attempt three or even only two. But there are rare situations. The Jitsi guys have no idea what could be the reason for that.