sbeliakou / playpit-labs Goto Github PK

Shell 53.48% PowerShell 46.52%

playpit-labs's Introduction

[DEPRECATED]

Every project approaches its end.

I'm proud that this platform (and the idea in general) helped a lot of engineers to upgrade 202x core skills = Docker and Kubernetes, I've got a lot of positive feedback. Dozens of ideas were put into the backlog.

The main reason why I'm stopping the support of this product - it's getting a lot of time and efforts

Playpit Labs: Local Hands-on Playground

Playpit-Labs is a learner-centric Training Platform which enables to facilitate a wide range of learning tasks (investigation, troubleshooting, development) via interactive module system.

Based on a hands-on experience, the Platform delivers scenario-related approach with instant feedback. So, the user can easily navigate his training path - learn, practice, instantly check the results and track the progress in the personal report in the course of a chosen technology or a tool (currently available courses - Docker and Kubernetes).

The Platform can be used either in a face-to-face training, an instructor-led training, a blended learning, or just a self-paced training to address multi-purpose demands.

Design of the course is aimed to provide a wide scope of scenarios to cover all the competency levels starting from the beginner and up to advance during a step-by-step learning process. Playpit-Labs is a kind of a virtual campus, where everyone can anytime and anywhere access the training materials and interact.

Check it out and try!

Main Features:

In-browser terminal window
Integrated web browsing facility
Easy navigation between tasks/scenarios
Instant feedback with scoring results
Tracking overall progress
Hundreds of development and troubleshooting scenarios
Changeable environment for various use cases
Full support of useful documentation

Architecture Specifics:

Docker-based (systemd) containers (Linux inside!!!)
Pre-baked configuration (as per lab purposes)
Fast and easy rolling out

System Requirements:

Please ensure that your local station meets the following requirements before using current product:

Docker (19+) or Docker Desktop (2.2+) installed
docker-compose (1.25+) installed
Use Chrome/Chromium Browser for stable work

Usage:

Here's a list of commands which bring this stand up and terminate local infrastructure.

Linux/MacOS Bash:

bash/start                 ## Getting Help
bash/start docker          ## starting Docker Lab
bash/start k8s             ## starting Kubernetes Lab
bash/stop                  ## Tearing it all down

Windows PowerShell:

Open powershell console as Administrator and execute:

Set-ExecutionPolicy Unrestricted  ## Getting an ability to execute pwsh scripts

! Important:

In Docker Desktop settings, uncheck General -> Use the WSL2 based engine:

The next step is:

pwsh\start.ps1             ## Getting Help
pwsh\start.ps1 docker      ## starting Docker Lab
pwsh\start.ps1 k8s         ## starting Kubernetes Lab
pwsh\stop.ps1              ## Tearing it all down

Lab URLs

Lab stand is available by the following addresses:

Labs

Docker (v19.03.6):

00 Basics
01 Images
02 Containers
03 Volumes
04 Networks
05 Compose
06 Limits
07 Extra
Playground

Kubernetes (v1.18.2):

00 Basics
01 Pods
02 Deployments
03 Services
04 Ingress
05 Volumes
06 ConfigMaps and Secrets
07 Helm
08 Cluster Creation with kubeadm
09 Bootstrapping Nodes with TLS
10 RBAC - User Access
Playground

Screen Shots

playpit-labs's People

Contributors

Stargazers

Watchers

playpit-labs's Issues

can't evaluate field ServerErrors in type types.Info

Hi, getting this error on the fresh installed Debian 10

root@debian:/opt/playpit-labs# ./bash/start
Checking Requirements:
docker is running       .. template: :1:3: executing "" at <.ServerErrors>: can't evaluate field ServerErrors in type types.Info
FAILED (is docker running?)

Docker is running:

root@debian:/opt/playpit-labs# service docker status
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2020-10-25 22:51:23 EDT; 1min 24s ago
     Docs: https://docs.docker.com
 Main PID: 371 (dockerd)
    Tasks: 18
   Memory: 149.9M
   CGroup: /system.slice/docker.service
           ├─371 /usr/sbin/dockerd -H fd://
           └─446 docker-containerd --config /var/run/docker/containerd/containerd.toml --log-level info

Oct 25 22:51:22 debian dockerd[371]: time="2020-10-25T22:51:22.903039144-04:00" level=warning msg="Your kernel does not support swap memory limit"
Oct 25 22:51:22 debian dockerd[371]: time="2020-10-25T22:51:22.903201372-04:00" level=warning msg="Your kernel does not support cgroup rt period"
Oct 25 22:51:22 debian dockerd[371]: time="2020-10-25T22:51:22.903310782-04:00" level=warning msg="Your kernel does not support cgroup rt runtime"
Oct 25 22:51:22 debian dockerd[371]: time="2020-10-25T22:51:22.903741762-04:00" level=info msg="Loading containers: start."
Oct 25 22:51:23 debian dockerd[371]: time="2020-10-25T22:51:23.054380298-04:00" level=info msg="Default bridge (docker0) is assigned with an IP ad
Oct 25 22:51:23 debian dockerd[371]: time="2020-10-25T22:51:23.103847779-04:00" level=info msg="Loading containers: done."
Oct 25 22:51:23 debian dockerd[371]: time="2020-10-25T22:51:23.145360910-04:00" level=info msg="Docker daemon" commit=4c52b90 graphdriver(s)=overl
Oct 25 22:51:23 debian dockerd[371]: time="2020-10-25T22:51:23.145999345-04:00" level=info msg="Daemon has completed initialization"
Oct 25 22:51:23 debian systemd[1]: Started Docker Application Container Engine.
Oct 25 22:51:23 debian dockerd[371]: time="2020-10-25T22:51:23.164817997-04:00" level=info msg="API listen on /var/run/docker.sock"

Access into a demo lab

Hi, is there any way to have access to some demo labs?

I would like to check how we can create our own courses on your platform and even contribute to more labs.

Thanks in advance.

The docker process doesn't work

Hi there.

I'm trying to execute docker commands in the platform's console but I cannot do this. The docker process is down. When I run

systemctl status docker

I get

● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2020-11-28 17:58:58 UTC; 10min ago
     Docs: https://docs.docker.com
  Process: 496 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.so>
 Main PID: 496 (code=exited, status=1/FAILURE)

Nov 28 17:58:58 docker-host systemd[1]: docker.service: Service RestartSec=2s expired, schedu>
Nov 28 17:58:58 docker-host systemd[1]: docker.service: Scheduled restart job, restart counte>
Nov 28 17:58:58 docker-host systemd[1]: Stopped Docker Application Container Engine.
Nov 28 17:58:58 docker-host systemd[1]: docker.service: Start request repeated too quickly.
Nov 28 17:58:58 docker-host systemd[1]: docker.service: Failed with result 'exit-code'.
Nov 28 17:58:58 docker-host systemd[1]: Failed to start Docker Application Container Engine.
Nov 28 17:59:14 docker-host systemd[1]: docker.service: Start request repeated too quickly.
Nov 28 17:59:14 docker-host systemd[1]: docker.service: Failed with result 'exit-code'.
Nov 28 17:59:14 docker-host systemd[1]: Failed to start Docker Application Container Engine.

My operating system is Windows 10.

Labs no access denied

The first stage was passed, but the second stage is not allowed.
Help me, please, this is product is very well.

How to start on Linux

~/../playpit-labs$ bash/start
bash: bash/start: /bin/bash^M: bad interpreter: No such file or directory

~/../playpit-labs$ bash bash/start
bash/start: line 2: $'\r': command not found
bash/start: line 3: syntax error near unexpected token $'{\r'' 'ash/start: line 3: function success() {

~/../playpit-labs$ sed -i 's/\r$//' bash/start
~/../playpit-labs$ bash bash/start docker
Checking Requirements:
docker is running .. FAILED (is docker running?)

~/../playpit-labs$ service docker status
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-05-18 10:17:07 +03; 2h 9min ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 1156 (dockerd)
Tasks: 17
Memory: 141.8M
CGroup: /system.slice/docker.service
└─1156 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

start host error

PS D:\Stude\PlayPit-Labs> pwsh\start.ps1 docker
Checking Requirements:
docker .. ok
docker is running .. ok
docker-compose .. ok
Cleaning Up
fe471e112de4
docker_root
Pulling updates
Pulling docker-host ... done Starting New Stack
Creating volume "docker_root" with default driver
Creating docker-host ... error
ERROR: for docker-host Cannot start service docker-host: Ports are not available: listen tcp 0.0.0.0:80: bind: An attempt was made to access a socket in a way forbidden by its access permissions.

ERROR: for docker-host Cannot start service docker-host: Ports are not available: listen tcp 0.0.0.0:80: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
ERROR: Encountered errors while bringing up the project.

Ready! Browse: http://lab.playpit.net:8081

PS D:\Stude\PlayPit-Labs\pwsh>