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
Copy file name to clipboardExpand all lines: docs/installation/fedora.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -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.
0 commit comments