This repository will be used for any docker code Template folder contains a base structure for building docker files
once docker machine is installed Docker Doc Docker Machine
docker-machine create --driver virtualbox default
docker-machine ls
docker-machine env default
eval $(docker-machine env default)
docker run busybox echo hello world # executes hello world on busybox container in default docker machine
docker run -d -p 8000:80 nginx # runs nginx on default machine inside docker container. container continues running.
docker-machine stop default # stops default machine
docker-machine start default
docker-machine ip default
docker-machine rm default* This one is not the best practice
* run vm (docker-machine create --driver virtualbox <name of machine>)
* bind shell to machine (eval $(docker-machine env <name of machine>))
* ensure machine is started (docker-machine ls
* start machine (docker-machine start <name of machine>)
* download image/os to docker-machine (docker pull alpine)
* run image (docker run -i -t alpine)
* if need to get into machine later (docker-ssh <node name>)
* adjust image from inside (mkdir average)
* add script [file in docker/average repo (vi average/average.js)
* save file
* get hostname of container should be a hash value (hostname) -or- (docker ps [from outside the container])
* leave containter (exit)
* save container changes [a sha2 hash will return] (docker commit -m "installed node and wrote average application" <container hostname>
* run command on new container image (docker run <container sha2 hash> averages/average.js 3 4 5)create Dockerfile
docker build <name> <dir> # build from Dockerfile directory and tagging a name [ex. docker build andrewnascimento/test .]docker network ls docker network create --driver bridge my-network
- bridge networks do not allow container linking (container linking [via --link] is deprecated)
- there is also overlay network
the -v will create a local volume for the data to persist through when the container is killed) - sharing volume between containers
docker run -d -p 5984:5984 -v $(pwd)/data:/usr/local/var/lib/couchdb --name new-couchdb klaemo/couchdb
## DIDN'T WORK IN EXAMPLE - must be versioning
# data volume containers - docker containers that house a volume to be shared between containers
docker create -v /usr/local/var/lib/couchdb --name db-data debian:jessie /bin/true
# won't show in $(docker ps) [will show in $(docker ps -a)]
docker ps -a
docker run -d -p 5984:5984 -v /usr/local/var/lib/couchdb --name db1 --volmes-from db-data klaemo/couchdb
docker run -d -p 5985:5984 -v /usr/local/var/lib/couchdb --name db2 --volumes-from db-data klaemo/couchdb
curl -X PUT http://192.168.99.100:5984/db
curl -H 'Content-Type: application/json' -X POST http://192.168.99.100:5984/db -d '{"value": "Hello OReilly"}'
curl http://192.168.99.100:5985/db/faeed6d7f714f9c140a0d5e98a00049e
## flocker?docker-compose up # starts all containers controlled by specific compose file
docker-compose stop # stops all containers controlled by specific compose file
docker-compose rm # kills all containers controlled by specific compose file
docker-compose up -d # detached start of all containers controlled by specific compose fileswarm Run containers across multiple docker hosts need backing keyvalue storage mechanism to keep track of nodes - console, etcd, zookeeper
docker-machine create --driver virtualbox
eval $(docker-machine env default)
docker run -d -p 2181:2181 --name zookeeper jplock/zookeeper
docker run -d -p 3376:3376 --name manager -t -v /var/lib/boot2docker:/certs:ro swarm manage -H tcp://0.0.0.0:3376 -tlsverify --tlscacert=/carts/ca.pem --tlscert==/certs/server.pem --tlskey=/certs/server-key.pem zk://192.168.99.100:2181
docker-machine create --driver virtualbox node1
eval $(docker-machine env default)
docker run -d swarm join --addr $(docker-machine ip node1):2376 zk://192.168.99.100:2181
docker-machine create --driver virtualbox node2
docker run -d swarm join --addr $(docker-machine ip node2):2376 zk://192.168.99.100:2181
eval $(docker-machine env default)
export DOCKER_HOST=192.168.99.100:3376
docker info
docker run -d -P rickfast/hello-oreilly-http
docker run -d -P rickfast/hello-oreilly-http
docker run -d -P rickfast/hello-oreilly-httpdocker run -d -p 2181:2181 jplock/zookeeper
docker-machine create -d virtualbox --swarm --swarm-master --swarm-discovery="zk://192.168.99.100:2181/swarm" --engine-opt="cluster-store=zk://192.168.99.100:2181/overlay" --engine-opt="cluster-advertise=eth1:2376" swarm-master
docker-machine create -d virtualbox --swarm --swarm-master --swarm-discovery="zk://192.168.99.100:2181/swarm" --engine-opt="cluster-store=zk://192.168.99.100:2181/overlay" --engine-opt="cluster-advertise=eth1:2376" node1
docker-machine create -d virtualbox --swarm --swarm-master --swarm-discovery="zk://192.168.99.100:2181/swarm" --engine-opt="cluster-store=zk://192.168.99.100:2181/overlay" --engine-opt="cluster-advertise=eth1:2376" node2
eval $(docker-machine env --swarm swarm-master)
docker network create --driver overlay overlay-net
docker run --name counter -p 4567:4567 -d --net=overlay-net --env="constraint:node==node1"
docker run --name redis -d --net=overlay-net --env="constraint:node==node2" redis
docker ps
curl http://192.168.99.105:4567 # use ip of node that counter container lives onkitematic - can be a useful UI tool
docker run --log-driver=json-file rickfast/hello-oreillydocker run --name splunk -p 8000:8000 -p 8088:8088 -d outcoldman/splunk:6.3.3
login to splunk at 192.168.99.100:8000 and create a sourcetype and generate an event collector token or enable tcp input. We used HTTP event collector and configured a token for this example
docker run --name hello --log-driver=splunk --log-opt splunk-token=72252C6F-1C8F-4134-8D88-E00C932A9AAF --log-opt splunk-url=http://192.168.99.100:8088 --log-opt splunk-sourcetype=docker rickfast/hello-oreilly