I have only deployed one escript in a docker container in the past, and to get around this issue of reading from ENV, I included a bash script, which was used as the docker entry point, and in this bash script I call the escript passing in any env vars the script needs as arguments like ./my_script --env-var $MY_ENV_VAR.
However, I suspect the forum may provide us with a better way 
