You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -39,7 +41,7 @@ Now you are ready to go with a little CI/CD Environment:
39
41
... not really, its all http .. don't worry about it! It's only local communication
40
42
41
43
##### security paranoia
42
-
All the exposed ports are reachable from outer world because docker creates and deletes dynamically FORWARD rules with default policy ACCEPT on startup / shutdown containers wich have exported ports.
44
+
All the exposed ports are reachable from outer world because docker creates and deletes dynamically iptables FORWARD rules with default policy ACCEPT on startup / shutdown containers wich have exported ports.
43
45
44
46
To deny acccess from outer world the DOCKER-USER Chain (since docker 17.06) ist the medium of choice for your own rules (this is the first target in the FORWARD-Chain and never touched by docker).
45
47
@@ -97,23 +99,19 @@ echo "See logs with prefix DCKR-EXT-ACCESS-DENY:"
97
99
* MAVEN_HOME is /opt/maven
98
100
* JAVA_HOME is /usr/lib/jvm/java-8-openjdk-amd64
99
101
* Blue Ocean is installed and works perfect with a GitHUB Account, not GitLab ... sorry, this is Jenkins.
100
-
You need to be logged in to use Blue Ocean
102
+
You need to be logged as a jenkins-user in to use Blue Ocean
101
103
102
104
### Giltab
103
105
104
-
* the docker-registry is at port 5555 (and secured with an openssl certificate ..thats part of
105
-
prepareCompose.sh), just create a project in gitlab and click at the registry tab to show
106
+
* the docker-registry from GitLab is at port 5555 (and secured with an openssl certificate ..thats part of
107
+
prepareEnvironment.sh), just create a project in gitlab and click at the registry tab to show
106
108
how to login to the project registry and how to tag your images
107
109
* ssh cloning and pushing is at port 2222
108
110
109
111
#### gitlab-runner
110
-
The runner is a gitlab-multirunner image with a docker-runner (concurrent=1) , based on [gitlab/gitlab-runner][2] The docker-compose section has an environment called
111
-
REGISTER_MODE, it can set to KEEP or REFRESH
112
-
* KEEP register at one time a runner and keep it during startups
113
-
* REFRESH at every startup remove all old runners and register one new runner (the pipeline-history ist lost.)
114
-
115
-
It takes a long time until gitlab is ready to accept a runner registration, if it fails, increase the REGISTER_TRYS
112
+
The runner is a gitlab-multirunner image with a docker-runner (concurrent=1) , based on [gitlab/gitlab-runner][2] at every startup any runner is removed and only ONE new runner ist registrated to avoid multiple runners (the pipeline-history maybe lost.) docker-in-docker works :-)
116
113
114
+
It takes a long time until gitlab is ready to accept a runner registration, if it fails, increase the REGISTER_TRYS in docker-compse.yml
0 commit comments