Elasticsearch production docker command not working at all, and when it works, it exits - docker

Question

I was following the tutorial for what should I do for when deploying elasticsearch for production, and I came up with these commands
docker run
-d
--name es01
-p 9200:9200
-p 9300:9300
--restart=unless-stopped
--ulimit nofile=65536:65536
-e "bootstrap.memory_lock=true"
--ulimit memlock=-1:-1
-e "discovery.type=single-node"
-e "cluster.name=es-cluster01"
-e "node.name=es01-node"
--mount source=elasticsearch,target=/usr/share/elasticsearch/data
elasticsearch:elasticsearch:8.6.1
-Xms4g -Xmx4g
This version of my docker command did not work, because of the -Xms4g -Xmx4g in the last part, it was unrecognized, I read in the production documentation that I should not use this command -e ES_JAVA_OPTS="-Xms1g -Xmx1g", but I am forced to use it in my second version since the alternative which is using -Xms4g -Xmx4g at the end of the command did not work, this is my 2nd attempt:
docker run
-d
--name es01
-p 9200:9200
-p 9300:9300
--restart=unless-stopped
--ulimit nofile=65536:65536
-e "bootstrap.memory_lock=true"
--ulimit memlock=-1:-1
-e "discovery.type=single-node"
-e "cluster.name=es-cluster01"
-e ES_JAVA_OPTS="-Xms1g -Xmx1g"
-e "node.name=es01-node"
--mount source=elasticsearch,target=/usr/share/elasticsearch/data
elasticsearch:elasticsearch:8.6.1
When I use this version, I get the following error which prevents elasticsearch installation from commencing:
"log.level":"ERROR", "message":"exception during geoip databases update",
So, in the end I came up with this version, where I removed -e ES_JAVA_OPTS="-Xms1g -Xmx1g" :
docker run
-d
--name es01
-p 9200:9200
-p 9300:9300
--restart=unless-stopped
--ulimit nofile=65536:65536
-e "bootstrap.memory_lock=true"
--ulimit memlock=-1:-1
-e "discovery.type=single-node"
-e "cluster.name=es-cluster01"
-e "node.name=es01-node"
--mount source=elasticsearch,target=/usr/share/elasticsearch/data
elasticsearch:elasticsearch:8.6.1
This version installs fine, without a problem, and I can see the default password and everything, and the docker container goes online, but the issue with this here is that, every 24 hours, it is unexpectedly exiting, without a log to show me what is wrong.
I used the command docker container inspect es01 and there is no error in STATUS.