# Best practice for build-time secrets?

**URL:** <https://community.fly.io/t/best-practice-for-build-time-secrets/7519>\
**Category:** Build debugging\
**Created:** [September 28, 2022, 8:16pm UTC](https://community.fly.io/t/best-practice-for-build-time-secrets/7519 "2022-09-28T20:16:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![fideloper-fly](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/fideloper-fly/32/3834_2.png) [@fideloper-fly](https://community.fly.io/u/fideloper-fly)\
**Post date:** [September 28, 2022, 11:28pm UTC](https://community.fly.io/t/best-practice-for-build-time-secrets/7519/2 "2022-09-28T23:28:36Z")

</div>

Hi!

Yep, the [build-time secrets documented here is the way](https://fly.io/docs/reference/build-secrets/) currently. We’ve had some internal discussions on if we can improve that - so that’s in process, but there’s no firm decisions on that yet.

Partially the build-time secrets are a bit annoying due to how Docker makes us “mount” secrets into a container. I’ve had a similar question about injecting them for you during the build step - It doesn’t seem like Docker gives us a way to “mount” secrets into the build due to how Docker exposes its API there (or we haven’t found it yet).

---

_[View the full topic](https://community.fly.io/t/best-practice-for-build-time-secrets/7519)._