# No .env file found with Docker compose

**URL:** <https://vaultwarden.discourse.group/t/no-env-file-found-with-docker-compose/1893>\
**Category:** Help\
**Created:** [September 24, 2022, 5:05am UTC](https://vaultwarden.discourse.group/t/no-env-file-found-with-docker-compose/1893 "2022-09-24T05:05:59Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![stefan0xC](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/stefan0xc/32/1765_2.png) [@stefan0xC](https://vaultwarden.discourse.group/u/stefan0xC)\
**Post date:** [September 26, 2022, 9:04pm UTC](https://vaultwarden.discourse.group/t/no-env-file-found-with-docker-compose/1893/3 "2022-09-26T21:04:54Z")

</div>

> [@Ironyn](#):
>
> vualtwarden shows there’s no .env file found

See BlackDex’ explanation: [I cannot figure out how to source the .env file - #4 by BlackDex](https://vaultwarden.discourse.group/t/i-cannot-figure-out-how-to-source-the-env-file/948/4)

The `.env` file mentioned in the logs is unrelated to the environment file used by docker (or systemd). While launching, vaultwarden checks for the existence of such a file in the current working directory of the container and simply informs you if it does not find it.

You could probably bind mount your `vaultwarden.env` file to `/.env` instead of specifying it as environment file for docker if you want to get rid of the message.

---

_[View the full topic](https://vaultwarden.discourse.group/t/no-env-file-found-with-docker-compose/1893)._