core dump, docker official image, export ERL_FLAGS=" -name couchdb "

[NOTE]: # ( ^^ Provide a general summary of the issue in the title above. ^^ )

## Description

When I run the official docker image using these environment variables it cores dump:

export COUCHDB_ERLANG_COOKIE=XXX
export COUCHDB_PASSWORD=XXX
export COUCHDB_SECRET=XXX
export COUCHDB_USER=admin
export ERL_FLAGS=" -name couchdb "

## Steps to Reproduce

```
$ docker run -ti --rm \
--env COUCHDB_ERLANG_COOKIE=JIxa5jYokaO2IlE5Hf1l \
--env COUCHDB_PASSWORD=password \
--env COUCHDB_SECRET=77qz5K82uAkbIrBFBsgG \
--env COUCHDB_USER=admin \
--env COUCHDB_VERSION=3.3.3 \
--env ERL_FLAGS=" -name couchdb " \
couchdb
{"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}})

Crash dump is being written to: erl_crash.dump...done
```

## Expected Behaviour

Should be able to run couchdb

## Your Environment

* CouchDB version used: 3.3.3
* Operating system and version: ubuntu:22.04

## Additional Context

The reason I need this is because I run couchdb in Kubernetes using the official helm chart. I also have a plain docker compose configuration in my local machine. When I copy the data from one environment to another I get the infamous error message "This database failed to load."

I read on different forums that the cluster name has to be the same in order for that work.

I can't find any documentation related unfortunately.

Start by reproducing the CouchDB 3.3.3 Docker command with ERL_FLAGS=" -name couchdb " and inspect the reported net_kernel nodistribution crash. Compare the official Docker image and Helm chart handling of Erlang node naming and document or correct the configuration so CouchDB starts and the expected cluster-name behavior is clear.

Written by the indexing model from the issue text.