Downloaded 65 times
![docker container stop [id]
docker container start [id]
docker container attach [id]](https://image.slidesharecdn.com/dockerfordummies-170515184813/85/Docker-for-Dummies-25-320.jpg)
![docker pull [image]
docker images
docker run [image]
docker container stop / start / attach
docker ps
docker search [something]](https://image.slidesharecdn.com/dockerfordummies-170515184813/85/Docker-for-Dummies-27-320.jpg)
Uploaded byRoel Hartman
Docker for Dummies
The document discusses the architectural differences between virtual machines (VMs) and Docker containers, emphasizing that Docker containers are lightweight, isolated environments that share operating system resources, leading to faster deployment and lower overhead. It outlines the advantages of Docker, including portability, scalability, and cost-efficiency, as well as providing an overview of Docker images and commands. Additionally, it highlights Docker's suitability for creating independent application building blocks and its growing support in software delivery, particularly for Oracle applications.
More Related Content
Docker for Dummies
- 2.
- 6.
- 7.
- 8.
- 9. And these arecontainers
- 10. Architectural differences server host OS hypervisor(VMWare) guest OS guest OS guest OS bins/ libs bins/ libs bins/ libs App A App A’ App B server host OS hypervisor (VMWare) guest OS guest OS guest OS bins/ libs bins/ libs bins/ libs App A App A’ App B bins/libs Docker Containers are isolated, but share OS and, where appropriate, bins/libraries … result is significantly faster deployment, much less overhead, easier migration, faster restart
- 11. •You can putanything in there •Stays locked •Efficient transport •No missing dependencies during deployments •You can run various versions of libraries •Reduce compatibily concerns
- 12. Pros of aDocker Container •Self contained - everything you need is in … •an isolated environment •and therefore highly portable •it runs everywhere - also in the cloud •it is (relatively) small and lightweight •therefore very scalable •and thus cost-efficient. So it’s not (just) aVM. It is a …
- 13.
- 14. It starts withan imageIt all starts with an image
- 17.
- 18. docker image • Afilesystem and parameters to use it at runtime (dockerfile) • It doesn't have state • All layers are readonly • Layers are shared between images • Update requires just a download of the new layer • “docker commit” to "save" changes, • add a new layer • create a newer image OS MySQL App
- 19.
- 20. • A (running)instance of an image • Adds a read/write layer on top of the image • Image is not cloned • Spin up dozens of containers readonly docker container OS MySQL App C1 read write C2 read write C3 read write
- 21.
- 22. docker run -itubuntu -i : interactive -t : tty
- 23. docker run -d -p 5000:5000 --namecatweb mikegcoleman/catweb -d : detach -p : port forwarding -- name
- 24.
- 25. docker container stop[id] docker container start [id] docker container attach [id]
- 26.
- 27. docker pull [image] dockerimages docker run [image] docker container stop / start / attach docker ps docker search [something]
- 29.
- 30.
- 32.
- 38.
- 39. docker run -d --name apex51 -p49160:22 -p 8080:8080 -p 1521:1521 -v /Users/Roel/docker:/tomcat/webapps/i/host araczkowski/oracle-apex-ords
- 40. APEX & Docker- Multiple containers DB Storage ORDS WebSocket server A.O.P. etc..
- 41.
- 42.
- 43. Docker take aways •Perfect for creating independent building blocks for your app • Perfect for simple software delivery • Invest some time to get acquainted with the architecture • Ideal replacement of your local developmentVM • Oracle’s support is growing
- 44. Hier geht eszur Vortragsbewertung: apex.doag.org http://bit.ly/2pzP15a Vielen Dank!
- 45.