annastopel 0a18aa3d09 Internal Docker registry host that is visible only inside teh cluster. ... cdi-func-test-registry-host - a host that runs docker registry and is accessible from inside the cluster via cdi-func-test-registry-host.kube-system host name. The registry is populated with images taken from /tmp/shared/images. It is used by functional tests. Example of usage: 1. inspect With skopeo acces registry to ispect image built from /tmp/shared/images/tinyCore.iso skopeo inspect --tls-verify=false docker://cdi-func-test-registry-host.kube-system/tinycore.iso 2. Copy skopeo copy --src-tls-verify=false docker://cdi-func-test-registry-host.kube-system/tinycore.iso dir:/tmp/download Technical details: Registry is run in a dedicated service cdi-func-test-registry-host. In the same pod there are 3 containers: 1. cdi-func-test-registry - runs registry:2 with self signed certificate that listens on port 443 2. cdi-func-test-registry-init - used to pouplate /tmp/shared/images volume with images created from /test/images/tinuCore.iso and with certificate generated during container image build 3. cdi-func-test-registry-populate - encapsulted all images of /tmp/shared/images in docker images and pushes them to the registry		2019-01-06 09:43:40 +02:00
..
Dockerfile	Internal Docker registry host that is visible only inside teh cluster.	2019-01-06 09:43:40 +02:00
registry-config.yml	Internal Docker registry host that is visible only inside teh cluster.	2019-01-06 09:43:40 +02:00
start-registry.sh	Internal Docker registry host that is visible only inside teh cluster.	2019-01-06 09:43:40 +02:00