Which lab is it that you're having issues with?
Lab: Docker for Java Developers

Description

When deploying Java applications in production one usually specifies the amount of memory available to the JVM (-Xmx) and other assorted configuration settings. Unfortunately, this is (usually) static configuration and therefore fixed in the container image. When specifying memory constraints

The "Tag" section on each guide can encourage use of them for better asset management.
In this case (running labs) we can use them to mark resources created during the lab and tear them down later more quickly.

The guide for goaccess has the following command:

[isabell@stardust ~]$ cp /etc/goaccess.conf ~/etc/goaccess.conf

This is wrong because the config file is located in /etc/goaccess/goaccess.conf (at least on kushida.uberspace.de)

Verison of PowerShell: 
$PSVersionTable.PSVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
5      1      17763  1007

PowerShell host:
Console

Operating system:
Get-CimInstance Win32_OperatingSystem | Select-Object Caption, Version, ServicePackMajorVersion, OSArchitecture, WindowsDirectory


Caption                 : Microsoft Windows Server 2019 Standard
V

The second cat command is missing the apiVersion line.
Should be:

cat <<EOF | kubectl apply -f -
apiVersion: networking.istio.io/v1alpha3

Also, in the current version of Istio, we need to run:

kubectl apply -f samples/bookinfo/networking/virtual-service-all-v1.yaml -n default
kubectl apply -f samples/bookinfo/networking/destination-rule-all-mtls.yaml -n default

instead

When we search for files to render, we should recursively check the given directory. Currently we only search the given directory.

docs/
  components/
    a.md
    b.md
  overview/
    installation.md

While working on another problem (#176), I realized I needed to add changes to kubeadm.cfg while instantiating a cluster. We already do this with the IPv6 deployment, and I can think of a few other things that would be nice to change here too.

I think there are 2 approaches here:

1. Add a template with all the kubeadm options, and build it out with some defaults that can override
2. Provi