Build, Release and Run Containers with Docker Compose

InstructorMark Shust

Share this video with your friends

Send Tweet

In this lesson we will cover proper version tagging when building Docker images, creating a docker-compose.yml file for proper release management, and running the tagged release by using Docker Compose to launch app resources as Docker containers.

uwinkler
~ 7 years ago

Great course! But is there one lesson missing? Where is the lesson how to write the Dockerfile?

Mark Shustinstructor
~ 7 years ago

Thank you! The Dockerfile referenced is just any Dockerfile you used to create your image. This course assumes some basic understanding of git, node & docker. I did have a complex time figuring out the best way to organize this course, and decided to create one video per one 12-factor concept (that's why there are 12 videos plus the intro video). So, things may seem a bit out of order, but that is organized chaos.

That said, I have many more Docker lessons available at:

https://egghead.io/instructors/mark-shust

You may be particularly interested in this one on how to build your own custom Docker image:

https://egghead.io/lessons/docker-build-your-own-custom-docker-image

Hope this helps!

Raja
~ 7 years ago

You just skipped a lesson on creating docker file?

Mark Shustinstructor
~ 7 years ago

See my last comment above.

Rapido
~ 6 years ago

This Video is breaking at 0:16 sec and unable to continue it. I thought it of some technical issue but still facing the problem for almost 50+ hours. Can we fix it?

Ryan Wessel
~ 4 years ago

I am running into some issues where docker-compose up -d app is not actually running my Docker container. If I run docker ps -a it appears, but the list is empty if I run docker ps. I am not experienced in Docker, so I might need to start with your other courses before this one.

Mark Shustinstructor
~ 4 years ago

I apologize for the belated reply! If an image is not showing with docker ps but is showing with docker ps -a, your container exited for what appears to be an unknown reason. You can diagnose this by running docker logs CONTAINER_ID, and then inspect the output from the container to try to find out what is going on and why the container has exited.