Docker:up & Running (reading notes, first half)

Docker:up & Running

2. C/s Model + Registry
4. 3 Large components: Compose (Fig), Machine,swarm
6. Bridge ("Docker0") <--> private subnets (available--net off, use the host address directly)
8. Stateless architecture: Should the database engine not be dived into the Docker container? VS ' stateful application '
   1. Stateless applications: Dependencies can be passed through environment variables (you may need to retrofit your existing app's code)
10. lightweight:1.4.1 12KB image?
12. Immutable infrastructure (+GC? ）
    1. Stack fs (unique hash): Similar to Git, this is a trend
    2. Image Tags: Easy to manage
14. Dockerfile: Each command produces a new FS layer (which guarantees the consistency of functionality, but security can have additional risks)
    1. From USER ENV RUN ADD workdir CMD
    2. $ docker run-d-P 8080:8080-e env1= "..." Example/node-hello:latest (Devops? The description here is a little unclear)
16. Deploying? Nonissue
18. Orchestration:swarm/centurion/helios-Kubernetes/mesos
20. Atomic Host:coreos (upgrade OS with just a simple reboot)
22. $ sudo ln-sf/usr/bin/docker.io/usr/local/bin/docker
    1. $ sudo docker-d -H unix:///var/run/docker.sock-h tcp://0.0.0.0:2375
    2. $ docker Run--rm-ti ubuntu:latest
24. Boot2docker? (For Mac and win platforms)
26. * Vagrant + CoreOS
28. Storage back-end (FS): AUFS,BTRFS,DEVICE-MAPPER,OVERLAYFS
30. Registry (versioned managed Docker image, slightly)

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Docker:up & Running (reading notes, first half)