docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Improvements to EE install for SLES (#5097)

This commit is contained in:
Misty Stanley-Jones 2017-11-06 14:34:26 -08:00 committed by GitHub
parent 91e75c3871
commit 8aee9fe189
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 67 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

82
engine/installation/linux/docker-ee/suse.md
View File

@ -39,17 +39,39 @@ Docker Community Edition (Docker CE) is not supported on SLES.
To install Docker EE, you need the 64-bit version of SLES 12.x. Docker EE is not
supported on OpenSUSE.
The only supported storage driver for Docker EE on SLES is `btrfs`, which will be
The only supported storage driver for Docker EE on SLES is Btrfs, which will be
used by default if the underlying filesystem hosting `/var/lib/docker/` is a
BTRFS filesystem.
#### Firewall configuration
Docker creates a `DOCKER` iptables chain when it starts. The SUSE firewall may
block access to this chain, which can prevent you from being able to run
containers with published ports. You may see errors such as the following:
```none
WARNING: IPv4 forwarding is disabled. Networking will not work.
docker: Error response from daemon: driver failed programming external
connectivity on endpoint adoring_ptolemy
(0bb5fa80bc476f8a0d343973929bb3b7c039fc6d7cd30817e837bc2a511fce97):
(iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 80 -j DNAT --to-destination 172.17.0.2:80 ! -i docker0: iptables: No chain/target/match by that name.
(exit status 1)).
```
If you see errors like this, adjust the start-up script order so that the
firewall is started before Docker, and Docker stops before the firewall stops.
See the
[SLES documentation on init script order](https://www.suse.com/documentation/sled11/book_sle_admin/data/sec_boot_init.html).
### Uninstall old versions
Older versions of Docker were called `docker` or `docker-engine`. If these are
installed, uninstall them, along with associated dependencies.
Older versions of Docker were called `docker` or `docker-engine`. If you use OS
images from a cloud provider, you may need to remove the `runc` package, which
conflicts with Docker EE. If these are installed, uninstall them, along with
associated dependencies.
```bash
$ sudo zypper rm docker docker-engine
$ sudo zypper rm docker docker-engine runc
```
If removal of the `docker-engine` package fails, use the following command
@ -64,16 +86,37 @@ It's OK if `zypper` reports that none of these packages are installed.
The contents of `/var/lib/docker/`, including images, containers, volumes, and
networks, are preserved. The Docker EE package is now called `docker-ee`.
## Configure the btrfs filesystem
## Configure the Btrfs filesystem
By default, SLES formats the `/` filesystem using BTRFS, so **most people do not
not need to do the steps in this section**. If the filesystem that
By default, SLES formats the `/` filesystem using Btrfs, so **most people do not
not need to do the steps in this section**. If you use OS images from a cloud
provider, you may need to do this step. If the filesystem that
hosts `/var/lib/docker/` is **not** a BTRFS filesystem, you must configure a
BTRFS filesystem and mount it on `/var/lib/docker/`:
BTRFS filesystem and mount it on `/var/lib/docker/`.
1. Format your dedicated block device or devices as a Btrfs filesystem. This
1. Check whether `/` (or `/var/` or `/var/lib/` or `/var/lib/docker/` if they
are separate mount points) are formatted using Btrfs. If you do not have
separate mount points for any of these, a duplicate result for `/` will be
returned.
```bash
$ df -T / /var /var/lib /var/lib/docker
```
You need to complete the rest of these steps **only if one of the following
is true**:
- You have a separate `/var/` filesystem that is not formatted with Btrfs
- You do not have a separate `/var/` or `/var/lib/` or `/var/lib/docker/`
filesystem and `/` is not formatted with Btrfs
If `/var/lib/docker` is already a separate mount point and is not formatted
with Btrfs, back up its contents so that you can restore them after step
3.
2. Format your dedicated block device or devices as a Btrfs filesystem. This
example assumes that you are using two block devices called `/dev/xvdf` and
`/dev/xvdg`.
`/dev/xvdg`. **Make sure you are using the right device names.**
> Double-check the block device names because this is a
destructive operation.
@ -86,7 +129,7 @@ BTRFS filesystem and mount it on `/var/lib/docker/`:
There are many more options for Btrfs, including striping and RAID. See the
[Btrfs documentation](https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices).
2. Mount the new Btrfs filesystem on the `/var/lib/docker/` mount point. You
3. Mount the new Btrfs filesystem on the `/var/lib/docker/` mount point. You
can specify any of the block devices used to create the Btrfs filesystem.
```bash
@ -96,6 +139,9 @@ BTRFS filesystem and mount it on `/var/lib/docker/`:
Don't forget to make the change permanent across reboots by adding an
entry to `/etc/fstab`.
4. If `/var/lib/docker` previously existed and you backed up its contents
during step 1, restore them onto `/var/lib/docker`.
## Install Docker EE
@ -190,7 +236,7 @@ from the repository.
Docker is installed but not started. The `docker` group is created, but no
users are added to the group.
4. Configure Docker EE to use the `btrfs` filesystem. **This is only required if
4. Configure Docker EE to use the Btrfs filesystem. **This is only required if
the `/` filesystem is not using BTRFS.** However, explicitly specifying the
`storage-driver` has no harmful side effects.
@ -226,6 +272,9 @@ commands. Continue to [Linux postinstall](linux-postinstall.md) to configure the
graph storage driver, allow non-privileged users to run Docker commands, and for
other optional configuration steps.
> **Important**: Be sure Docker is configured to start after the system
> firewall. See [Firewall configuration](#firewall-configuration).
#### Upgrade Docker EE
To upgrade Docker EE:
@ -267,8 +316,8 @@ need to download a new file each time you want to upgrade Docker EE.
Docker is installed but not started. The `docker` group is created, but no
users are added to the group.
4. Configure Docker EE to use the `btrfs` filesystem. **This is only required if
the `/` filesystem is not using BTRFS.** However, explicitly specifying the
4. Configure Docker EE to use the Btrfs filesystem. **This is only required if
the `/` filesystem is not using Btrfs.** However, explicitly specifying the
`storage-driver` has no harmful side effects.
Edit the file `/etc/docker/daemon.json` (create it if it does not exist) and
@ -303,6 +352,9 @@ commands. Continue to [Post-installation steps for Linux](linux-postinstall.md)
to allow non-privileged users to run Docker commands and for other optional
configuration steps.
> **Important**: Be sure Docker is configured to start after the system
> firewall. See [Firewall configuration](#firewall-configuration).
#### Upgrade Docker EE
To upgrade Docker EE, download the newer package file and repeat the
@ -326,7 +378,7 @@ instead of `zypper install`, and pointing to the new file.
```
If you used a separate BTRFS filesystem to host the contents of
`/var/lib/docker/`, you can unmount and format the `btrfs` filesystem.
`/var/lib/docker/`, you can unmount and format the Btrfs filesystem.
You must delete any edited configuration files manually.