Signed-off-by: Oriol Francès <oriolfa@gmail.com>
| ... | ... |
@@ -83,3 +83,26 @@ and volumes run the following command: |
| 83 | 83 |
$ rm -rf /var/lib/docker |
| 84 | 84 |
|
| 85 | 85 |
You must delete the user created configuration files manually. |
| 86 |
+ |
|
| 87 |
+## Issues |
|
| 88 |
+ |
|
| 89 |
+### systemd-network |
|
| 90 |
+ |
|
| 91 |
+Users of systemd-network >= v220 who have configured their network manually by |
|
| 92 |
+creating an `<interface>.network` file in `/etc/systemd/network/` may have to add |
|
| 93 |
+the following line to make sure IP Forwarding is not disabled: |
|
| 94 |
+ |
|
| 95 |
+``` |
|
| 96 |
+[Network] |
|
| 97 |
+... |
|
| 98 |
+IPForward=kernel |
|
| 99 |
+... |
|
| 100 |
+``` |
|
| 101 |
+ |
|
| 102 |
+From systemd-network v220 onwards, the forwarding setting for a given network |
|
| 103 |
+defaults to *off* (instead of not being set). This prevents IP Forwarding to |
|
| 104 |
+happen, since docker only enables `net.ipv4.conf.all.forwarding` (which is |
|
| 105 |
+overriden by `net.ipv4.conf.<interface>.forwarding` being disabled) |
|
| 106 |
+ |
|
| 107 |
+Adding `IPForward=kernel` to the `<interface>.network` file prevents this |
|
| 108 |
+behavior, allowing IP Forwarding to function as expected. |