# Create own Docker compose

**URL:** <https://forums.docker.com/t/create-own-docker-compose/23572>\
**Category:** General\
**Created:** [October 18, 2016, 7:23am UTC](https://forums.docker.com/t/create-own-docker-compose/23572 "2016-10-18T07:23:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tote](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tote](https://forums.docker.com/u/tote)\
**Post date:** [October 18, 2016, 7:23am UTC](https://forums.docker.com/t/create-own-docker-compose/23572/1 "2016-10-18T07:23:50Z")

</div>

Hello,

I hear a lot about docker and was playing around with docker container and images and I do like docker a lot, but I do not find an answer yet for what I want for myself.  
At the moment, I am working with vagrant and VM, but I think docker would be a better choice for the future.

But I do not find my way in, to make my own special docker container and images.  
I have read about composer and do container for my own purpose.  
What I do have in mind is a “basic” Docker container with for example Typo3 with my own extensions, DB, gulp, path etc, which I can edit and refactor for the next use.

Is there any articels/tuts how to achieve this goal you can recommend me?

Thank you

regards

Torsten

---

<div class="post-metadata">

**Author:** ![dmaze](https://avatars.discourse-cdn.com/v4/letter/d/ea5d25/32.png) [@dmaze](https://forums.docker.com/u/dmaze)\
**Post date:** [October 18, 2016, 10:27am UTC](https://forums.docker.com/t/create-own-docker-compose/23572/2 "2016-10-18T10:27:35Z")

</div>

> [@tote](#):
>
> But I do not find my way in, to make my own special docker container and images.

Have you read through [[Overview of the get started guide | Docker Docs](https://docs.docker.com/engine/getstarted/step_four/)](“Build your own image”) and the rest of the official “Get Started with Docker” guide?

> [@](#):
>
> What I do have in mind is a “basic” Docker container with for example Typo3 with my own extensions, DB, gulp, path etc, which I can edit and refactor for the next use.

Almost all of the containers I’ve seen have been fairly lightly customized and they tend to only do a single thing. I’d recommend against trying to install a database in a container; instead, use the standard `mysql` or `postgres` or `mariadb` images in your Docker Compose file. Install your JavaScript application in a separate image. Within the context of a specific image, it’s often easier to install software into, say, `/usr/local` and leave `$PATH` alone.

Do use `docker build`, a lot. Do commit your `Dockerfile` to source control. Don’t use `docker commit`.

---

<div class="post-metadata">

**Author:** ![tote](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@tote](https://forums.docker.com/u/tote)\
**Post date:** [October 19, 2016, 9:17am UTC](https://forums.docker.com/t/create-own-docker-compose/23572/3 "2016-10-19T09:17:42Z")

</div>

Hello Dave,

thank you very much for your hint.

I think, this will help me, to get a better understanding.

regards

Torsten