<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Docker :: Cloud Platform Journey</title>
    <link>/basics/index.html</link>
    <description>Discover Docker:&#xA;Validation of your Docker environment Docker container Docker images Docker network Docker volumes Docker cleanup Alternative Image Builds</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate>
    <atom:link href="/basics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Validation</title>
      <link>/basics/validation/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/basics/validation/index.html</guid>
      <description>Before starting the class, let’s make sure if things are up and running as they should.&#xA;Prerequisites Make sure you are logged in to your attendee VM or any other valid Docker environment.&#xA;Exercise - Help and Options Open your terminal application and run the plain docker command in order to display a generic help message and available options:&#xA;docker&#xA;Exercise - Version To get some information about the version of your Docker installation run:</description>
    </item>
    <item>
      <title>Container</title>
      <link>/basics/container/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/basics/container/index.html</guid>
      <description>Exercise - List container and images In order to look up whether you have any containers, execute the following command:&#xA;docker container ls&#xA;As you have just started with the lab, the list of containers is empty.&#xA;$ docker container ls CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES Info docker container ls and docker ps are identical commands&#xA;In order to check whether you already have any local images, execute the following command:</description>
    </item>
    <item>
      <title>Images</title>
      <link>/basics/images/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/basics/images/index.html</guid>
      <description>Exercise - Build your image using commit (Optional) To recap the essentials from the Container Exercises run a container in detached mode, using port mapping, environment variables and a custom name (base_container):&#xA;docker run -d -p 8080:8080 -e PROPERTY=Stuttgart --name base_container novatec/technologyconsulting-hello-container:v0.1&#xA;Milestone: DOCKER/IMAGES/BUILD-COMMIT&#xA;and validate if the container is doing what it is supposed to do:&#xA;curl localhost:8080/hello; echo&#xA;Hello World (from 34f40588f2e0) to Stuttgart Containers are basically isolated processes. To find out more about this execute the ps command in the following way:</description>
    </item>
    <item>
      <title>Network</title>
      <link>/basics/network/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/basics/network/index.html</guid>
      <description>Exercise - Network introduction As a result of the “Images” exercise you can now see the following containers in your list:&#xA;docker ps&#xA;$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES b2a968f4f4b0 postgres:latest &#34;docker-entrypoint.s…&#34; 6 minutes ago Up 6 minutes 0.0.0.0:5432-&gt;5432/tcp, :::5432-&gt;5432/tcp postgresdb d266fc71ab06 todoui:v0.1 &#34;/__cacert_entrypoin…&#34; 8 minutes ago Up 8 minutes 0.0.0.0:8090-&gt;8090/tcp, :::8090-&gt;8090/tcp todoui 265da979af36 todobackend:v0.1 &#34;/__cacert_entrypoin…&#34; 12 minutes ago Up 12 minutes 0.0.0.0:8080-&gt;8080/tcp, :::8080-&gt;8080/tcp todobackend If you pick the backend container and execute a shell, you will be able to find out that there is no connection between the instances.</description>
    </item>
    <item>
      <title>Volumes</title>
      <link>/basics/volumes/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/basics/volumes/index.html</guid>
      <description>Data Persistence Without Volumes In this chapter we are going to take a look at how to persist data with docker.&#xA;First we want to observe how data behaves in docker containers with the setup we have so far and no additional steps taken towards data persistence.&#xA;Subtask 1: Create a PostgreSQL Container without Volumes Let’s start removing the old and creating a new database. While the previously created database is working fine, we want to illustrate the differences between starting a database with and without volume more clearly. Therefore, remove the old database first by running docker rm -f postgresdb.</description>
    </item>
    <item>
      <title>Clean up</title>
      <link>/basics/cleanup/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/basics/cleanup/index.html</guid>
      <description>Exercise - Clean up You will not need the running containers after this, so clean up the environment before proceeding:&#xA;To stop all running containers execute:&#xA;docker ps -q | xargs docker stop&#xA;To remove all containers run:&#xA;docker ps -a -q | xargs docker rm&#xA;The network we created also still exists:&#xA;docker network ls&#xA;NETWORK ID NAME DRIVER SCOPE 10b9448cc71d bridge bridge local 2d2089ec09bd host host local 81e8bb2089d0 none null local 3ba6a91f405b todonet bridge local To remove the network use:</description>
    </item>
    <item>
      <title>Alternative Image Builds</title>
      <link>/basics/build/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/basics/build/index.html</guid>
      <description>About This lab will walk you through steps to build container images with various technologies.&#xA;Validation Validate Java installation.&#xA;java --version Should display output like (version might differ):&#xA;openjdk 17.0.9 2023-10-17 OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-120.04) OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-120.04, mixed mode, sharing) Dockerfile Exercises In this part of the exercise multiple options to use Dockerfiles will be shown and applied.</description>
    </item>
  </channel>
</rss>