Page Menu
Home
DevCentral
Search
Configure Global Search
Log In
Files
F3717027
D1755.id4460.diff
No One
Temporary
Actions
View File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Award Token
Flag For Later
Size
954 B
Referenced Files
None
Subscribers
None
D1755.id4460.diff
View Options
diff --git a/KNOWN_ISSUES.md b/KNOWN_ISSUES.md
--- a/KNOWN_ISSUES.md
+++ b/KNOWN_ISSUES.md
@@ -44,25 +44,3 @@
$ grep -q pefs_load /boot/loader.conf || cat >> /boot/loader.conf
pefs_load="YES"
```
-
-## Role: paas-docker
-
-### Set static IP addresses
-
-Docker slave nodes for Jenkins should use known addresses, either static IP,
-either a DNS system. Such advanced network configuration through Salt requires
-2018.3.0.
-
-**Workaround**
-
-Two workarounds are straightforward:
-
- - `docker inspect apsile | grep 172` and manually set the IP in Jenkins.
- - run an internal DNS service for the Docker engine and containers,
- e.g. through the phensley/docker-dns container (see T958 for plan)
-
-The second is recommended if you restart or reprovision often,
-with containers declared in the pillar in a different order each time.
-
-The first should be stable as long as you append new containers
-to the pillar docker_containers entry end.
File Metadata
Details
Attached
Mime Type
text/plain
Expires
Wed, Nov 6, 23:40 (21 h, 52 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
2232254
Default Alt Text
D1755.id4460.diff (954 B)
Attached To
Mode
D1755: Mark as fixed the Jenkins slave adressing issue
Attached
Detach File
Event Timeline
Log In to Comment