Skip to main content

Docker



if you and your friend have vm and want to sync up you may have to transfer 20gb of file. but with docker docker diff to check the difference then docker commit then docker push which will only be the change.

docker containers: are actual containers running the applications and includes os, user added files, and meta data

docker images: helps to launch docker containers

docker file: is a file containing instructions that help automate image creation

layer: each file system that is stacked when docker mounts rootfs.

Install docker using:

sudo rpm install docker

docker commands:

docker pull: pull a pre-built image from public repos

docker run: run in 3 modes background,foreground,interactive

docker logs: logs of running logs

docker commit: save container state

docker images: list of all images

docker diff: changes in files and directories

docker build: build docker images from

dockerfiles

docker inspect: low level info about containers

docker attach: interact with running container

docker kill: kill a container

it is beneficial to separate every server like in lamp have separate php, mysql,apache in diff containers

you can use a supervisor -n to it

docker file:

automates image creation process

set of instruction to create an image

syntax: instruction argument

how docker files different:

dockerfiles run in layers

after every command a new layer is created.

if there is a mistake in line 29 of 30 if you corect in docker then first 28 skip because already run and just resolving the issue.

Dockerfile commands:

MAINTAINER <author name> sets autho name

RUN <command> execute command

ADD <src><dest> copy files from one location to another

from local machine to inside docker

CMD["executable","param1","param2"] provides default for executing container

EXPOSE <port>port on which container might get deprecated

ENTRYPOINT ["executable","param1"...] configure container as exe from where you want to start execution

WORKDIR /path set working dir

ENV <key> <value> set env variables

USER <uid> set UID for use when running an image

VOLUME ["/data"] enable access to a directory from a working container mount from host to docker

docker create   -----using dockerfile

Layering issue with dockerfile is that docker is restarted after every command you will losse any environment variable

If you want to run a if then you will have to write it on a single line.



you can override this in command line

if container when you execute CMD  and command as main command and if that command quits or goes in background.



boot2docker to bootstrap instead of chef


Comments

Popular posts from this blog

Terraform

Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions. Configuration files describe to Terraform the components needed to run a single application or your entire datacenter. Terraform generates an execution plan describing what it will do to reach the desired state, and then executes it to build the described infrastructure. As the configuration changes, Terraform is able to determine what changed and create incremental execution plans which can be applied. The infrastructure Terraform can manage includes low-level components such as compute instances, storage, and networking, as well as high-level components such as DNS entries, SaaS features, etc. The key features of Terraform are: Infrastructure as Code : Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and...

Salt stack issues

The function “state.apply” is running as PID Restart salt-minion with command:  service salt-minion restart No matching sls found for ‘init’ in env ‘base’ Add top.sls file in the directory where your main sls file is present. Create the file as follows: 1 2 3 base: 'web*' : - apache If the sls is present in a subdirectory elasticsearch/init.sls then write the top.sls as: 1 2 3 base: '*' : - elasticsearch.init How to execute saltstack-formulas create file  /srv/pillar/top.sls  with content: base : ' * ' : - salt create file  /srv/pillar/salt.sls  with content: salt : master : worker_threads : 2 fileserver_backend : - roots - git gitfs_remotes : - git://github.com/saltstack-formulas/epel-formula.git - git://github.com/saltstack-formulas/git-formula.git - git://github.com/saltstack-formulas/nano-formula.git - git://github.com/saltstack-f...

Helm: Installation and Configuration

PREREQUISITES You must have Kubernetes installed. We recommend version 1.4.1 or later. You should also have a local configured copy of  kubectl . Helm will figure out where to install Tiller by reading your Kubernetes configuration file (usually  $HOME/.kube/config ). This is the same file that  kubectl  uses. To find out which cluster Tiller would install to, you can run  kubectl config current-context or  kubectl cluster-info . $ kubectl config current-context my-cluster INSTALL HELM Download a binary release of the Helm client. You can use tools like  homebrew , or look at  the official releases page . For more details, or for other options, see  the installation guide . INITIALIZE HELM AND INSTALL TILLER Once you have Helm ready, you can initialize the local CLI and also install Tiller into your Kubernetes cluster in one step: $ helm init This will install Tiller into the Kubernetes cluster you saw with  kubectl config current-context . TIP:  Want to install into a different cl...