Following @cles commit #6bd15a68c for Arch
Signed-off-by: yyekhlef <yyekhlef@gmail.com>
(cherry picked from commit f224a9f3d609eec8bff9c6be18582eb72cd0e7ef)
... | ... |
@@ -206,6 +206,22 @@ If you need to add an HTTP Proxy, set a different directory or partition for the |
206 | 206 |
Docker runtime files, or make other customizations, read our Systemd article to |
207 | 207 |
learn how to [customize your Systemd Docker daemon options](/articles/systemd/). |
208 | 208 |
|
209 |
+## Running Docker with a manually-defined network |
|
210 |
+ |
|
211 |
+If you manually configure your network using `systemd-network` with fedora version 22, containers you start with Docker may be unable to access your network. |
|
212 |
+Beginning with version 220, the forwarding setting for a given network (`net.ipv4.conf.<interface>.forwarding`) defaults to *off*. This setting prevents IP forwarding. It also conflicts with Docker which enables the `net.ipv4.conf.all.forwarding` setting within a container. |
|
213 |
+ |
|
214 |
+To work around this, edit the `<interface>.network` file in |
|
215 |
+`/usr/lib/systemd/network/` on your Docker host (ex: `/usr/lib/systemd/network/80-container-host0.network`) add the following block: |
|
216 |
+ |
|
217 |
+``` |
|
218 |
+[Network] |
|
219 |
+... |
|
220 |
+IPForward=kernel |
|
221 |
+... |
|
222 |
+``` |
|
223 |
+ |
|
224 |
+This configuration allows IP forwarding from the container as expected. |
|
209 | 225 |
|
210 | 226 |
## Uninstall |
211 | 227 |
|