Linux containers and Docker have been all the rage in sysOps for quite some time now. Come to this session to learn about how you can or if you should be using them, and to learn about container technologies, how thy differ from VMs and if they truly are the future. Take a look at Docker basics and get an understanding of how it can be used as part of your workflow, not just for development, but for production deployments as well. We will also bust some Myths surrounding container technologies and Docker.

1. CAN YOU CONTAIN THE FUTURE: Docker,
Container Technologies, The Future, And You
BY: CURT GRATZ

9. ‣ Getting started with
Docker
‣ Why you should contain
everything in containers
that contain things
‣ Everything about Docker
‣ The Batman Equation
What we won’t be covering

10. ‣ Learn about containers and how they differ from Vms
‣ Learn the pros and cons of using containers
‣ A little about Docker and how to integrate it into your
workflow
‣ Learn how you can use Docker for easy deployments
‣ Bust some Myths about container technologies and
Docker.
What we will be covering

11. ‣ Husband
‣ Dad
‣ Coach
‣ Youth Leader
‣ Co-Owner of Computer Know How
‣ Member of Team ColdBox
‣ Lover of Open Source
The Obligatory Who Am I?

12. Lets talk about you

14. YOU? A DEVELOPER?

15. YOU? A SYS ADMIN?

16. YOU? DEV OPS?

17. YOU? AN ACCOUNTANT?

18. YOU? MARKETING?

19. YOU? MANAGER?

20. YOU? DBA?

21. YOU? QA/TESTER?

22. YOU? FULL STACK?

24. Lets talk about containers

25. Matrix of Hell

26. It works on my machine

27. How shipping solved the problem

28. How containers solve the problem

29. Traditional VM VS Containers

30. Pros and Cons of Containers

31. Isolation

33. Startup times

34. Size

35. CPU and Memory usage

36. Its a container

37. Deciding between containers and VMs

38. More then just Docker

41. Commands for images
‣ $ docker images # shows all images.
‣ $ docker import # creates an image from a tarball.
‣ $ docker build # creates image from Dockerfile.
‣ $ docker commit # creates image from a container.
‣ $ docker rmi # removes an image.
‣ $ docker history # list changes of an image.

42. Commands for Dockerfile
‣ FROM - The image the new image will be based on.
‣ COPY - Copy a file or dir into the image
‣ ADD - Like copy, but can be a URL or unpack a tar
‣ RUN - Ran a command inside the container
‣ ONBUILD - Run commands when building
‣ CMD - Default command to run
‣ ENV - Set a environment variable
‣ EXPOSE - expose a port
‣ VOLUME - Specify that a directory should be stored outside the union file
system

43. Commands for containers
‣ $ docker create # creates a container but does not start it.
‣ $ docker run # creates and starts a container.
‣ $ docker stop # stops it.
‣ $ docker start # will start it again.
‣ $ docker restart # restarts a container.
‣ $ docker rm # deletes a container.
‣ $ docker kill # sends a SIGKILL to a container.
‣ $ docker exec # executes a command in a running container.

44. Commands for inspecting
‣ $ docker ps # shows running containers.
‣ $ docker inspect # info on a container (incl. IP address).
‣ $ docker logs # gets logs from container.
‣ $ docker events # gets events from container.
‣ $ docker port # shows public facing port of container.
‣ $ docker top # shows running processes in container.
‣ $ docker diff # shows changed files in container's FS.
‣ $ docker stats # shows metrics, memory, cpu, filsystem

45. Deployments

46. Build Once, Run Anywhere

47. Cattle, not Pets

48. Contract between Dev and Ops

49. Why it is important to get it right

50. Deployments

51. Deployments

52. node-app-service.yaml
apiVersion: v1
kind: Service
metadata:
name: node-app-service
spec:
ports:
- port: 3000
protocol: TCP
nodePort: 30061
selector:
name: node-app
type: LoadBalancer

53. node-app-rc.yaml
apiVersion: v1
kind: ReplicationController
metadata:
name: node-app-rc
spec:
replicas: 4
selector:
name: node-app
template:
metadata:
labels:
name: node-app
spec:
containers:
- name: node-app
image: privateRepo.private.com/image-name
ports:
imagePullSecrets:
- name: node-app

54. Start it up
‣ kubectl create -f node-app-service.yaml
‣ kubectl create -f node-app-rc.yaml

55. Scale it you say
‣ kubectl scale rc node-app --replicas=20

57. Containers Are Best Understood
as Small VMs

59. Containers Aren’t Suitable for
Critical Workloads

61. Containers Aren’t as Secure as
Traditional Infrastructure

63. Containers Cannot Be Deployed
and Orchestrated At Scale

65. Microservices are mandatory

67. Containers use less CPU and
Memory

69. Developers don’t want to deploy
apps and define infrastructure

71. Lets talk about the future

72. Containers are an old idea.

73. Containers are here to stay

74. Microservices grow in popularity

75. Standards and Maturity

76. Community on the rise

77. ‣ Logging
‣ None
‣ json-file
‣ syslog
‣ jourald
‣ fluent
Other topics not covered

78. ‣ Secrets
‣ Kubernetes
‣ Vault (open source by HashCorp)
‣ Keywhiz (open source by Square)
‣ Conjur (commercial)
Other topics not covered

79. ‣ Service Discovery
‣ Kubernetes
‣ Consul
‣ Etcd
‣ Zookeeper
Other topics not covered

80. ‣ Metrics
‣ Monitoring
‣ Networking
‣ Stateful services
Other topics not covered

81. “Thank you.”
–hold up applause sign here

82. ‣ Email - gratzc@compknowhow.com
‣ Blog - http://www.compknowhow.com/blog/
‣ Twitter - gratzc
‣ Skype - gratzc
‣ Snapchat - gratzc
‣ League of Legends - gratzc
Contact Info