I have identified the configuration issue causing the 13-second kernel boot delay and require community guidance on the proper solution.
Current Situation
I am starting my release without EPMD using the following vm.args configuration:
-start_epmd false
For this configuration to function within the Docker container, I must also set the ERL_DIST_PORT environment variable. Without this variable, the system generates the following error during boot:
Protocol 'inet_tcp': register/listen error: econnrefused
This error condition results in the kernel application requiring approximately 13 seconds to complete initialization, presumably because the system attempts multiple connection retries before proceeding with startup.
Performance Comparison
When I remove the -start_epmd false setting and allow EPMD to start normally, the release boots efficiently with the kernel application completing initialization in approximately 3 seconds.
...
{apply,{application,start_boot,[kernel,permanent]}}
{done_in_microseconds,3082918}
Request for Assistance
I require guidance on the proper configuration approach for running Erlang releases without EPMD in Docker containers while maintaining optimal boot performance. The current requirement for the ERL_DIST_PORT environment variable suggests there may be additional configuration parameters or alternative approaches that would eliminate both the connection errors and the associated startup delays.
I would appreciate any insights from the community regarding best practices for EPMD-disabled deployments in containerized environments that achieve the same performance characteristics as EPMD-enabled configurations.