gebruik dezelfde docker container voor java applicaties tijdens ontwikkelen en in de cloud
Download
Skip this Video
Download Presentation
Gebruik dezelfde Docker container voor Java applicaties tijdens ontwikkelen en in de cloud

Loading in 2 Seconds...

play fullscreen
1 / 65

Gebruik dezelfde Docker container voor Java applicaties tijdens ontwikkelen en in de cloud - PowerPoint PPT Presentation


  • 113 Views
  • Uploaded on

Gebruik dezelfde Docker container voor Java applicaties tijdens ontwikkelen en in de cloud. Johan Janssen, Info Support. Content. Continuous delivery Docker Jenkins Questions. Continuous Delivery. Automate everything Software quality Continuous improvement Regular deployments

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Gebruik dezelfde Docker container voor Java applicaties tijdens ontwikkelen en in de cloud' - nissim-gallagher


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
gebruik dezelfde docker container voor java applicaties tijdens ontwikkelen en in de cloud

Gebruik dezelfde Docker container voor Java applicaties tijdens ontwikkelen en in de cloud

Johan Janssen, Info Support

content
Content
  • Continuous delivery
  • Docker
  • Jenkins
  • Questions
continuous delivery
Continuous Delivery
  • Automate everything
  • Software quality
  • Continuous improvement
  • Regular deployments
  • Anyone can deploy
deployment pipeline
Deployment pipeline

Setup environment

Quality checks

Version control

Compile

Testing

Deployments

Etcetera

DevOps

End users

focus of this presentation
Focus of this presentation
  • Automate environment provisioning
  • Automate application deployment
why docker
Why Docker
  • To enable continuous delivery
  • Quickly provision environments
  • Run the same software local and in the cloud
  • Easy to move software
    • Better performance
    • Higher availability
    • Cheaper
docker vs virtual machines
Docker vs Virtual Machines
  • Disk space efficiency
  • Memory efficiency
  • Speed
  • Compatibility (run anywhere)
  • Isolation
  • Versioning
  • Internet of Things (Raspberry Pi etc.)
docker vs provisioning tools
Docker vs provisioning tools
  • Simple general commands
  • No Domain Specific Language (DSL)
  • Configuration with operating system commands
docker activity
Docker activity
  • Since March 2013
  • 8741 commits in 15 months
  • More than 460 570 contributors
  • Downloaded 2.75 13 million times
  • More than 14000 30000 Dockerized apps
  • >6500 Docker related projects on GitHub
  • More than 90 user groups
  • DockerCon (Europe)
  • Support from Google, VMWare, RackSpace, Red Hat, IBM, Microsoft etcetera
my first docker container
My first Docker container
  • Docker on Ubuntu 14.04

apt-get install docker.io

docker.io run -i -t ubuntu:saucy /bin/bash

dockerfiles directory structure
Dockerfiles directory structure
  • Main directory
    • BuildAndRunScript.sh
    • GeneralBase
      • Dockerfile
    • Sonar
      • Dockerfile
dockerfile generalbase
DockerfileGeneralBase

FROM ubuntu:saucy

RUN apt-get -y install software-properties- common

RUN add-apt-repository ppa:webupd8team/java

RUN apt-get update && apt-get -y upgrade

RUN echo "oracle-java7-installer shared/accepted-oracle-license-v1-1 boolean true" | debconf-set-selections

RUN apt-get -y install oracle-java7-installer

ENV JAVA_HOME /usr/lib/jvm/java-7-oracle

dockerfile sonar
Dockerfile Sonar

FROM GeneralBase

RUN apt-get install -y wget unzip

RUN wget http://dist.sonar.codehaus.org/sonarqube-4.2.zip

RUN unzip sonarqube-4.2.zip -d /opt

RUN rm sonarqube-4.2.zip

EXPOSE 9000

EXPOSE 9092

CMD ["/opt/sonarqube-4.2/bin/linux-x86-64/sonar.sh", "console", "/bin/bash"]

build
Build
  • Create the Dockerfiles
  • Build the containers:

<optional>cd GeneralBase

docker.io build -t GeneralBase .

cd .. </optional>

cd Sonar

docker.io build -t Sonar .

slide27
Run
  • Start the container

docker.io run -p 9000:9000

–p 9092:9092 -d Sonar

list all in active containers
List all in(active) containers

# docker.io ps –a

CONTAINER ID: ecbecf77461b

CREATED: 32 minutes ago

STATUS: Up 32 minutes

PORTS: 0.0.0.0:9000->9000/tcp, 0.0.0.0:9092->9092/tcp

controlling containers
Controlling containers
  • Start / stop / restart

docker [start/stop/restart] containerid

  • Follow SystemOut and SystemErr

docker logs -f containerid

controlling containers1
Controlling containers
  • Show (running) containers

dockerps –a

  • Show processes running in container

docker top containerid

  • Show changes in the container

docker diff containerid

controlling containers2
Controlling containers
  • Stop all containers

docker.io stop $(docker.io ps -a -q)

  • Remove all containers

docker.io rm $(docker.io ps -a -q)

  • Remove all images

docker.io rmi $(docker.io images -q)

data volumes
Data volumes
  • Dockerfile

ENV JENKINS_HOME /var/JenkinsData

  • Docker commands

docker.io run -v /var/JenkinsData –name

JenkinsDataContainerubuntu:saucy true

docker.io run -p 8080:8080 --volumes-from

JenkinsDataContainer -d Jenkins

diskspace
Diskspace

# docker.io images --tree

└─ 179.9 MB Tags: ubuntu:saucy

└─253.6 MB

└─741.8 MB Tags: GeneralBase:latest

└─763.6 MB Tags: AppServerBase:latest

├─763.6 MB Tags: EnvironmentP:latest

└─865.6 MB Tags: Nexus:latest

└─808.3 MB Tags: Gitblit:latest

└─901.5 MB Tags: Sonar:latest

└─805.4 MB Tags: Jenkins:latest

execution time
Execution time

real 4m11.729s

user 0m3.329s

sys 0m10.054s

docker registry
Docker registry
  • Creating the Docker registry

docker run -p 5000:5000 registry

docker client 1 push
Docker client 1 (push)
  • Modify container
  • Commit

docker.io commit 064f

192.168.56.31:5000/test-version-0.2

  • New containerid -> ff7e
  • Push

docker.io push

192.168.56.31:5000/test-version-0.2

docker client 2 pull
Docker client 2 (pull)
  • Pull

docker.io pull 192.168.56.31:5000/

test-version-0.2

  • Run

docker.io run -i -t ff7e /bin/bash

  • View the changed container
pull update only
Pull update only

docker images -tree

└─153b 194.2 MB test-version-0.1:latest

docker pull 192.168.56.31:5000/test-version-0.2

ff7e: Download complete

153b: Download complete

docker images -tree

└─153b 194.2 MB test-version-0.1:latest

└─ff7e 194.2 MB test-version-0.2:latest

why jenkins
Why Jenkins
  • Simple to use
  • Really popular
    • Used in many organizations
    • Regular updates
    • Big community creating plugins etc.
  • Most developers already use it
automatic versus manual deployment
Automatic versus manual deployment

Continuous deployment

Continuous delivery

keep it simple
Keep it simple

“Life is really simple, but we insist on making it complicated.”

- Confucius

slide59
Tips
  • Use a (private) Docker registry
  • Use images from the registry instead of export
  • Keep environmental settings separate
  • Use Jenkins to manage everything
  • Do not add extra functionality like OpenSSH
  • Think about topics such as security, monitoring and logging
  • Separate concerns in separate containers
  • Inherit containers
questions
Questions

[email protected]

http://blogs.infosupport.com/author/johanj/

ad