Files
container.training/slides/containers/Training_Environment.md
2025-11-15 07:57:14 +01:00

3.5 KiB

class: title

Our training environment

SSH terminal


Our training environment

  • If you are attending a tutorial or workshop:

    • a VM has been provisioned for each student
  • If you are doing or re-doing this course on your own, you can:


Our Docker VM

This section assumes that you are following this course as part of a tutorial, training or workshop, where each student is given an individual Docker VM.

  • The VM is created just before the training.

  • It will stay up during the whole training.

  • It will be destroyed shortly after the training.

  • It comes pre-loaded with Docker and some other useful tools.


Connecting to your Virtual Machine

You need an SSH client.

  • On OS X, Linux, and other UNIX systems, just use ssh:
$ ssh <login>@<ip-address>

Checking your Virtual Machine

Once logged in, make sure that you can run a basic Docker command:

.small[

$ docker version
Client:
 Version:       18.03.0-ce
 API version:   1.37
 Go version:    go1.9.4
 Git commit:    0520e24
 Built:         Wed Mar 21 23:10:06 2018
 OS/Arch:       linux/amd64
 Experimental:  false
 Orchestrator:  swarm

Server:
 Engine:
  Version:      18.03.0-ce
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.4
  Git commit:   0520e24
  Built:        Wed Mar 21 23:08:35 2018
  OS/Arch:      linux/amd64
  Experimental: false

]

If this doesn't work, raise your hand so that an instructor can assist you!


Installing Docker

  • "Installing Docker" really means "Installing the Docker Engine and CLI".

  • The Docker Engine is a daemon (a service running in the background) —— it manages containers, the same way that a hypervisor manages VMs.

  • We interact with the Docker Engine by using the Docker CLI.

  • The Docker CLI and the Docker Engine communicate through an API.

  • There are many other programs and client libraries which use that API.


class: pic

Docker Architecture


Can we run Docker locally?

  • If you already have Docker (or Podman) installed, you can use it!

  • The VMs can be convenient if:

    • you can't/won't install Docker or Podman on your machine,

    • your local internet connection is slow.

  • We're going to download many container images and distribution packages.

  • If the class takes place in a venue with slow WiFi, this can slow us down.

  • The remote VMs have good connectivity and downloads will be fast there.

(Initially, we provided VMs to make sure that nobody would waste time with installers, or because they didn't have the right permissions on their machine, etc.)