# Is "fly launch --dockerfile" safe to use with untrusted Dockerfiles?

**URL:** <https://community.fly.io/t/is-fly-launch-dockerfile-safe-to-use-with-untrusted-dockerfiles/23655>\
**Category:** General\
**Tags:** machines, flyctl, security, builders, login-only\
**Created:** [January 26, 2025, 6:10pm UTC](https://community.fly.io/t/is-fly-launch-dockerfile-safe-to-use-with-untrusted-dockerfiles/23655 "2025-01-26T18:10:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![v-yanakiev](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/v-yanakiev/32/46898_2.png) [@v-yanakiev](https://community.fly.io/u/v-yanakiev)\
**Post date:** [January 26, 2025, 6:10pm UTC](https://community.fly.io/t/is-fly-launch-dockerfile-safe-to-use-with-untrusted-dockerfiles/23655/1 "2025-01-26T18:10:14Z")

</div>

As part of a system to run untrusted user code, I’ve considered allowing users to define their own execution environments using a Dockerfile.

So: is calling “fly launch --dockerfile pathToUserDockerfile --name someUserApp” safe? That is, is there some Dockerfile that would allow a user to gain control of the machine calling “fly launch”?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\
**Post date:** [February 2, 2025, 9:28pm UTC](https://community.fly.io/t/is-fly-launch-dockerfile-safe-to-use-with-untrusted-dockerfiles/23655/3 "2025-02-02T21:28:20Z")

</div>

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