Elasticsearch fails to start after install with custom paths, possible BUG

when installing elasticsearch with custom paths set in /etc/elasticsearch/elasticsearch.yml and no other change this throws a very uninformative and annoying error.

systemd-entrypoint\[13576\]: ERROR: Unable to create logs dir \[/srv/elastic/log\], with exit code 78

the binary /usr/share/elasticsearch/bin/systemd-entrypoint can be manually invoked to no avail

changes made were to set in elasticsearch.yml

 path:
      data: /srv/elastic/esdata
      logs: /srv/elastic/eslogs
      repo: /srv/elastic/esrepo

eventually the ‘Unable to create’ issue is a read issue of sorts

try either of

chmod 750 /src/elastic
chmod 755 /src/elastic

when this error should continue to occur

assure the ownership is set

chmod -R elasticsearch:elasticsearch /srv/elastic

though i’m not yet confident that’s a sane ownership permission to set
my guess is

chmod -R root:elasticsearch /srv/elastic

could work too

crazy part is this issue was not resolved until the permission is manually set
reinstalled multiple times, also when remove all possible folders

eventually the process to stuck on a node.lock file, which was fixed after

rm /srv/elastic/data/node.lock
systemctl restart elasticsearch

I don't know if those are typos, but /src/... != /srv/...

Outside that, I do not really understand what's the possible bug you are reporting? if you set custom paths, you need to set ownership/perms correctly? What am I missing/misunderstanding?