github.com/portworx/docker@v1.12.1/docs/installation/linux/fedora.md (about) 1 <!--[metadata]> 2 +++ 3 aliases = [ "/engine/installation/fedora/"] 4 title = "Installation on Fedora" 5 description = "Instructions for installing Docker on Fedora." 6 keywords = ["Docker, Docker documentation, Fedora, requirements, linux"] 7 [menu.main] 8 parent = "engine_linux" 9 weight=-3 10 +++ 11 <![end-metadata]--> 12 13 # Fedora 14 15 Docker is supported on Fedora version 22, 23, and 24. This page instructs you to install 16 using Docker-managed release packages and installation mechanisms. Using these 17 packages ensures you get the latest release of Docker. If you wish to install 18 using Fedora-managed packages, consult your Fedora release documentation for 19 information on Fedora's Docker support. 20 21 ## Prerequisites 22 23 Docker requires a 64-bit installation regardless of your Fedora version. Also, your kernel must be 3.10 at minimum. To check your current kernel 24 version, open a terminal and use `uname -r` to display your kernel version: 25 26 $ uname -r 27 3.19.5-100.fc21.x86_64 28 29 If your kernel is at an older version, you must update it. 30 31 Finally, is it recommended that you fully update your system. Please keep in 32 mind that your system should be fully patched to fix any potential kernel bugs. Any 33 reported kernel bugs may have already been fixed on the latest kernel packages 34 35 36 ## Install 37 38 There are two ways to install Docker Engine. You can install with the `dnf` package manager. Or you can use `curl` with the `get.docker.com` site. This second method runs an installation script which also installs via the `dnf` package manager. 39 40 ### Install with DNF 41 42 1. Log into your machine as a user with `sudo` or `root` privileges. 43 44 2. Make sure your existing dnf packages are up-to-date. 45 46 $ sudo dnf update 47 48 3. Add the yum repo yourself. 49 50 $ sudo tee /etc/yum.repos.d/docker.repo <<-'EOF' 51 [dockerrepo] 52 name=Docker Repository 53 baseurl=https://yum.dockerproject.org/repo/main/fedora/$releasever/ 54 enabled=1 55 gpgcheck=1 56 gpgkey=https://yum.dockerproject.org/gpg 57 EOF 58 59 4. Install the Docker package. 60 61 $ sudo dnf install docker-engine 62 63 5. Enable the service. 64 65 $ sudo systemctl enable docker.service 66 67 6. Start the Docker daemon. 68 69 $ sudo systemctl start docker 70 71 7. Verify `docker` is installed correctly by running a test image in a container. 72 73 74 $ sudo docker run hello-world 75 Unable to find image 'hello-world:latest' locally 76 latest: Pulling from hello-world 77 a8219747be10: Pull complete 78 91c95931e552: Already exists 79 hello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security. 80 Digest: sha256:aa03e5d0d5553b4c3473e89c8619cf79df368babd1.7.1cf5daeb82aab55838d 81 Status: Downloaded newer image for hello-world:latest 82 Hello from Docker. 83 This message shows that your installation appears to be working correctly. 84 85 To generate this message, Docker took the following steps: 86 1. The Docker client contacted the Docker daemon. 87 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. 88 (Assuming it was not already locally available.) 89 3. The Docker daemon created a new container from that image which runs the 90 executable that produces the output you are currently reading. 91 4. The Docker daemon streamed that output to the Docker client, which sent it 92 to your terminal. 93 94 To try something more ambitious, you can run an Ubuntu container with: 95 $ docker run -it ubuntu bash 96 97 For more examples and ideas, visit: 98 http://docs.docker.com/userguide/ 99 100 101 ### Install with the script 102 103 104 1. Log into your machine as a user with `sudo` or `root` privileges. 105 106 2. Make sure your existing dnf packages are up-to-date. 107 108 $ sudo dnf update 109 110 3. Run the Docker installation script. 111 112 $ curl -fsSL https://get.docker.com/ | sh 113 114 This script adds the `docker.repo` repository and installs Docker. 115 116 4. Enable the service. 117 118 $ sudo systemctl enable docker.service 119 120 5. Start the Docker daemon. 121 122 $ sudo systemctl start docker 123 124 6. Verify `docker` is installed correctly by running a test image in a container. 125 126 $ sudo docker run hello-world 127 128 ## Create a docker group 129 130 The `docker` daemon binds to a Unix socket instead of a TCP port. By default 131 that Unix socket is owned by the user `root` and other users can access it with 132 `sudo`. For this reason, `docker` daemon always runs as the `root` user. 133 134 To avoid having to use `sudo` when you use the `docker` command, create a Unix 135 group called `docker` and add users to it. When the `docker` daemon starts, it 136 makes the ownership of the Unix socket read/writable by the `docker` group. 137 138 >**Warning**: The `docker` group is equivalent to the `root` user; For details 139 >on how this impacts security in your system, see [*Docker Daemon Attack 140 >Surface*](../../security/security.md#docker-daemon-attack-surface) for details. 141 142 To create the `docker` group and add your user: 143 144 1. Log into your system as a user with `sudo` privileges. 145 146 2. Create the `docker` group. 147 148 `sudo groupadd docker` 149 150 3. Add your user to `docker` group. 151 152 `sudo usermod -aG docker your_username` 153 154 4. Log out and log back in. 155 156 This ensures your user is running with the correct permissions. 157 158 5. Verify your work by running `docker` without `sudo`. 159 160 $ docker run hello-world 161 162 If you need to add an HTTP Proxy, set a different directory or partition for the 163 Docker runtime files, or make other customizations, read our Systemd article to 164 learn how to [customize your Systemd Docker daemon options](../../admin/systemd.md). 165 166 ## Running Docker with a manually-defined network 167 168 If you manually configure your network using `systemd-network` with `systemd` version 219 or higher, containers you start with Docker may be unable to access your network. 169 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. 170 171 To work around this, edit the `<interface>.network` file in 172 `/usr/lib/systemd/network/` on your Docker host (ex: `/usr/lib/systemd/network/80-container-host0.network`) add the following block: 173 174 ``` 175 [Network] 176 ... 177 IPForward=kernel 178 # OR 179 IPForward=true 180 ... 181 ``` 182 183 This configuration allows IP forwarding from the container as expected. 184 185 ## Uninstall 186 187 You can uninstall the Docker software with `dnf`. 188 189 1. List the package you have installed. 190 191 $ dnf list installed | grep docker 192 docker-engine.x86_64 1.7.1-0.1.fc21 @/docker-engine-1.7.1-0.1.fc21.el7.x86_64 193 194 2. Remove the package. 195 196 $ sudo dnf -y remove docker-engine.x86_64 197 198 This command does not remove images, containers, volumes, or user-created 199 configuration files on your host. 200 201 3. To delete all images, containers, and volumes, run the following command: 202 203 $ rm -rf /var/lib/docker 204 205 4. Locate and delete any user-created configuration files.