# Docker - Elastic Agent - must be provided as an absolute path

**URL:** <https://discuss.elastic.co/t/docker-elastic-agent-must-be-provided-as-an-absolute-path/317523>\
**Category:** Elastic Agent\
**Tags:** fleet\
**Created:** [October 26, 2022, 1:29pm UTC](https://discuss.elastic.co/t/docker-elastic-agent-must-be-provided-as-an-absolute-path/317523 "2022-10-26T13:29:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vecjh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vecjh/32/112545_2.png) [@vecjh](https://discuss.elastic.co/u/vecjh)\
**Post date:** [October 26, 2022, 1:29pm UTC](https://discuss.elastic.co/t/docker-elastic-agent-must-be-provided-as-an-absolute-path/317523/1 "2022-10-26T13:29:46Z")

</div>

Hi, this seems inconsistent. I can reference value for all variables in the docker compose using relative paths. Like in the official Elastic Docker guide:

`xpack.security.http.ssl.key=certs/es01/es01.key`

However, I cannot do the same with variables for `docker.elastic.co/beats/elastic-agent`.

If I set, say, `- FLEET_SERVER_ELASTICSEARCH_CA=certs/ca/ca.crt`. Then I get in the log:

`Error: --fleet-server-es-ca must be provided as an absolute path`

And yes, I'm mounting the same volume which is shared with ES node.

```auto
    volumes:
      - certs:/usr/share/elasticsearch/config/certs
      - /var/run/docker.sock:/var/run/docker.sock:ro

```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 23, 2022, 1:30pm UTC](https://discuss.elastic.co/t/docker-elastic-agent-must-be-provided-as-an-absolute-path/317523/2 "2022-11-23T13:30:35Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.