# Docker-compose for the win

**URL:** <https://openziti.discourse.group/t/docker-compose-for-the-win/1434>\
**Category:** Uncategorized\
**Created:** [July 27, 2023, 6:45pm UTC](https://openziti.discourse.group/t/docker-compose-for-the-win/1434 "2023-07-27T18:45:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jptechnical](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/jptechnical/32/1089_2.png) [@jptechnical](https://openziti.discourse.group/u/jptechnical)\
**Post date:** [July 27, 2023, 6:45pm UTC](https://openziti.discourse.group/t/docker-compose-for-the-win/1434/1 "2023-07-27T18:45:34Z")

</div>

I just wanted to share my win. I got a working, and repeatable, docker-compose setup going last night. It uses the simplified docker-compose document, and has the correct entries for the domain name. I confirmed by enrolling a couple of agents as well. It directs the `/persistent` folder to the same folder as the compose file.

I use the docs in the actual ziti/ziti repo and built from there. I believe it still uses the quickstart image. I have seen quite a few different lists of ENVs for this, so I will make an issue for a way I think the code can be simplified and self-documenting to reduce confusion… just a small tweak.

Thanks for all the help, I think I can start learning ziti in earnest now!

---

<div class="post-metadata">

**Author:** ![gberl002](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/gberl002/32/333_2.png) [@gberl002](https://openziti.discourse.group/u/gberl002)\
**Post date:** [July 27, 2023, 7:01pm UTC](https://openziti.discourse.group/t/docker-compose-for-the-win/1434/2 "2023-07-27T19:01:30Z")

</div>

That’s awesome, glad to hear it. Thank you for all of your feedback and for pointing out a few bugs on our end.