Charity  Ferry

Charity Ferry


Stacker Cli: Docker Compose Templates


Docker Compose Templates

Stacker is a simple tool for defining application environments, aka stacks. Each stack is optimized for development and for production use as well. Stacker is built on top of Docker and Docker Compose as an abstraction layer. The main paradigm followed in designing Stacker was convention over configuration.

📺 Demo


🏁 Installation

Requirements: node 6+, docker 17+, docker-compose 1.10+. Tested succesfully on Mac OS and Ubuntu.

Install the CLI app globally using NPM.

# install stacker
npm install -g stacker-cli

# make sure it's working
stacker --version

🔥 Getting Started

Before going further, make sure you cd into the root path of your project (cd ~/Projects/test-project).

Generate the stacker.yaml file

$ stacker init

If your project already has a stacker.yaml file, this step is not required.

Setup the project on your local machine

$ stacker link

This will do several things

  • create a local IP alias (eg.
  • setup your chosen domain name in /etc/hosts
  • add the project to the projects list

Build and start your application

$ stacker up

After this you will be able to reach your application using the domain name you choose previously. (eg.

✋ Add your favorite stack!

Is your stack missing? Please open an issue and we'll take care of it. Since we're not experts in all stacks, your input and guidance will be helpful to make a top notch stack. For the moment, we will keep all the stacks inside the official repos just to make sure they all follow best practices.

Here is a list of the stacks we want to add with your help: Symfony, Ruby on Rails, Django, Meteor, Play, Ghost. If you have other stacks in mind just let us know.

📝 Documentation

For full CLI reference, checkout the file.

📜 License

MIT @ Stacker

Download Details:

Author: stacker
Source code:
License: MIT license
#docker #javascript

What is GEEK

Buddha Community

Stacker Cli: Docker Compose Templates
Iliana  Welch

Iliana Welch


Docker Explained: Docker Architecture | Docker Registries

Following the second video about Docker basics, in this video, I explain Docker architecture and explain the different building blocks of the docker engine; docker client, API, Docker Daemon. I also explain what a docker registry is and I finish the video with a demo explaining and illustrating how to use Docker hub

In this video lesson you will learn:

  • What is Docker Host
  • What is Docker Engine
  • Learn about Docker Architecture
  • Learn about Docker client and Docker Daemon
  • Docker Hub and Registries
  • Simple demo to understand using images from registries

#docker #docker hub #docker host #docker engine #docker architecture #api

Jerod  Durgan

Jerod Durgan


How To Build A Kubernetes Backend In Compose CLI ?

Docker Compose is a great tool from Docker, it is used by millions to deploy and manage multi-containers applications. Docker Compose is basically 2 things:

  • The Compose file is a specification in yaml (named docker-compose.yaml by default) that Docker Compose takes as input. This file defines the components of a containerized application and how they are connected together. It should be written according to the Compose specification whose details are available in this repository
  • Docker Compose is the tool that processes this Compose file: it checks that it is written according to the Compose specification and deploys the application components

Anca Iordache from Docker, explains the move to the Compose Spec into the open and how she has started to develop a kube backend for the Compose CLI as a side project:

“The Compose format is very popular among developers due to its simplicity and there was always a lot of interest in having tools to deploy Compose files on platforms other than a single Docker Engine or Swarm. To make Compose go beyond Docker and Swarm, early in 2020, we opened the Compose specification to enable anybody to build tools around it. We used the new open specification and reference libraries to build support for Amazon ECS and Microsoft ACI into the Docker CLI for deploying Compose apps on these platforms. An obvious next target was Kubernetes as it is highly popular and there is a lot of interest in deploying Compose apps onto it. We wrote an initial proof of concept to test this integration but it hasn’t been added to Docker’s product roadmap yet. I have picked it up as my hack project to continue making progress with this integration. The current code for the Kubernetes backend can be found in the public repository docker/compose-cli and everybody is welcome to contribute to it.”

#kubernetes #docker #docker-compose #compose cli

August  Murray

August Murray


Top 24 Docker Commands Explained with Examples

In my previous blog post, I have explained in detail how you can Install Docker and Docker-compose on Ubuntu

In this guide, I have explained the Top 24 Docker Commands with examples.

Make sure you have sudo or root privileges to the system.

Docker Commands

  1. The command to check the version of Docker installed.
  2. To look/search for available docker images from the Docker registry.
  3. To pull docker images from the Docker registry.
  4. Listing all the docker images
  5. Creating / Running docker container from Docker image.
  6. To list the actively running docker containers.
  7. To list all the docker containers
  8. To stop a Container
  9. To start a Container
  10. To restart a Docker container
  11. To login to running Docker container
  12. To delete the stopped Docker containers
  13. To delete Docker images from the Local system
  14. To check logs of a running Docker container
  15. Killing docker containers
  16. Log in to Docker Hub registry (
  17. Removing docker hub registry login from the system.
  18. Check active resource usage by each containers
  19. Rename a Docker container
  20. To display system wide information of Docker
  21. Inspecting a Docker container
  22. Building docker images from Docker file
  23. Creating new docker images from a Container
  24. Pushing Docker images from Local to Docker registry.

#docker #docker-command #containers #docker-compose #docker-image

Cómo instalar Drupal con Docker Compose


Docker позволяет легко помещать приложения и службы в контейнеры, чтобы их можно было запускать где угодно. Однако при работе с Docker можно легко накопить чрезмерное количество неиспользуемых образов, контейнеров и томов данных, замедляющих работу и потребляющих место на диске.

Docker предоставляет все необходимые инструменты для очистки системы из командной строки. В этом руководстве с полезными советами кратко описываются полезные команды для освобождения места на диске и организации системы посредством удаления неиспользуемых образов, контейнеров и томов Docker.

Использование этого руководства:

  • Это руководство в формате полезных советов содержит автономные сниппеты для командной строки
  • Вы можете перейти к любому разделу, актуальному для задачи, которую вы пытаетесь выполнить.

Синтаксис замены команды command $(``command``), используемый в командах, доступен во многих популярных оболочках, включая bash, zsh и Windows Powershell.

Очистка всех неиспользуемых или не связанных с контейнерами образов, контейнеров, томов и сетей

В Docker имеется команда, очищающая все не связанные с контейнерами ресурсы, в том числе образы, контейнеры, тома и сети:

docker system prune

Чтобы удалить все остановленные контейнеры и неиспользуемые образы (а не только образы, не связанные с контейнерами), добавьте в эту команду флаг -a:

docker system prune -a

Удаление образов Docker

Удаление одного или нескольких конкретных образов

Используйте команду docker images с флагом -a, чтобы найти идентификатор удаляемых образов. Эта команда покажет вам все образы, включая промежуточные слои образов. Когда вы определитесь с составом удаляемых образов, вы можете передать их идентификаторы или теги в docker rmi:


docker images -a


docker rmi Image Image

Удаление образов, не привязанных к контейнеру

Образы Docker состоят из нескольких слоев. Несвязанные образы — это слои, не имеющие связей с каким-либо образами с тегами. У них нет никакого назначения, и они просто занимают место на диске. Их можно найти, добавив флаг фильтра -f со значением dangling=true в команду docker images. Если вы уверены, что хотите удалить их, вы можете использовать команду docker images purge:

#drupal #docker #docker compose #docker images

Loma  Baumbach

Loma Baumbach


Deploy a Tomcat Application Using Docker-Compose

In this blog, we will learn what is docker-compose and how we can deploy a tomcat application which uses mysql database. We will learn how we can setup a development environment using docker-compose in a single command


  1. Docker and Docker-compose installed


  • Docker-compose is a tool which is used to deploy multi-container application.
  • One single yaml file to deploy your application on the server.
  • Best suited for the developers to setup their workstation in a single command without installing any kind of dependencies for the application
  • docker-compose up to start your application
  • docker-compose down to clean up all the docker containers

Let’s take an example here:

We have a project called user registration which uses mysql for storing the data . In terms of microservices, we can say that we have two services as shown below:

  • Web Service
  • Database Service

You can clone this git repo and try the below example

Explanation of docker-compose

  1. **version : **This is the version as per the docker engine you have installed on your machine
  2. **services: **This is the main tag which is used to configure multiple services and under that we have details of all the services

3. web: This is our service name -> using image, ports and volumes

4. **volumes: **To store the database files

Now we will create main docker-compose file which will together launch a tomcat, mysql and phpmyadmin container

Tomcat container — To run your application

**Database container **— To store the data

PhpMyAdmin — Access the database through GUI

So we will have three services

  1. db — we are using local path to store the data so that when you run docker-compose down all your data will retain. If you use the volume then all data will get lost if you run the docker-compose down

Also, we are importing sql file so that our database is ready with the sample data. It is good so that each developer will always have the base or the actual data to run their application on the local machine

2. phpmyadmin — which is used to access the database through GUI and it depends on service db

3. web — which is used to access your web application and it also depends on service db

version: '3.3'
     image: mysql:5.7
       - /opt/test:/var/lib/mysql
       - ./mysql-dump:/docker-entrypoint-initdb.d
       MYSQL_DATABASE: testdb1
       MYSQL_USER: testuser
       MYSQL_PASSWORD: root
       - 3306:3306
      - db
    image: phpmyadmin/phpmyadmin
      - '8081:80'
      PMA_HOST: db
      - db
    image: tomcat
      - ./target/LoginWebApp-1.war:/usr/local/tomcat/webapps/LoginWebApp-1.war
      - '8082:8080'
      MYSQL_DATABASE: testdb1
      MYSQL_USER: testuser
      MYSQL_PASSWORD: root

#docker-compose #docker-image #docker