Get Started
Get Started
Welcome! We are excited that you want to learn Docker. The Docker Get Started Tutorial teaches you how to:
Set up your Docker environment (on this page) Build an image and run it as one container Scale your app to run multiple containers Distribute your app across a cluster Stack services by adding a backend database Deploy your app to production Get Started, Part 1: Orientation and setup
Get Started :: Part 1 :: Orientation
user@workstation:~$ docker --version
Docker version 17.12.1-ce, build 7390fc6user@workstation:~$ sudo docker info
Containers: 3
Running: 0
Paused: 0
Stopped: 3
Images: 2
Server Version: 17.12.1-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9b55aab90508bd389d7654c4baf173a981477d55
runc version: 9f9c96235cc97674e935002fc3d78361b696a69e
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.13.0-36-generic
Operating System: Ubuntu 16.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.55GiB
Name: workstation
ID: DLNC:VNQA:EV5K:B7Y5:NDAK:EWZW:JEFE:QQWF:HITS:LF5I:6577:7UMM
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
user@workstation:~$Get Started :: Part 2 :: Containers
Dockerfile defines what goes on in the environment inside your container. Access to resources like networking interfaces and disk drives is virtualized inside this environment, which is isolated from the rest of your system, so you need to map ports to the outside world, and be specific about what files you want to “copy in” to that environment. However, after doing that, you can expect that the build of your app defined in this Dockerfile behaves exactly the same wherever it runs.
Last updated